From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A4D5542DBA; Mon, 3 Jul 2023 01:36:15 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 3426B40EF0; Mon, 3 Jul 2023 01:36:15 +0200 (CEST) Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mails.dpdk.org (Postfix) with ESMTP id EC2EA40156 for ; Mon, 3 Jul 2023 01:36:13 +0200 (CEST) Received: by mail-pj1-f43.google.com with SMTP id 98e67ed59e1d1-26339ef4212so2782838a91.1 for ; Sun, 02 Jul 2023 16:36:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20221208.gappssmtp.com; s=20221208; t=1688340973; x=1690932973; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=g0JKGAaU0M6DI0blLqFva8m+lu2PaciyDl3AZ3Wwrs4=; b=HQqB5wiSlbxWpJg4DHOonkIk1+FVQgKS3MOztFbgoQRVJSPA3gFGMf0lAxbdKegCYm odhepeLp5m3znzl8GbzVzUjcJbozNBzXavB/lgseiSsg2rLiM+p65rGx6AiWfVFTuJDj HQCY/3ZLMVD/OMyDwQ7btkTc5BM9/9gvrnHy3epcNo5957vqtVqkQtgBjwVQun8W5Yru yD9EUJ6/qpEYTgOIVkR70vB2BrgHvW3eULk9l8Zj6RwGOnpLSPvlYVDPHpMJaKgeZSkr ZzPawVG6JakzbtBOXNtjGIJQfJvgOKRmlhoQF6T0ZE7vHpaUpGv6D91JmE1XAWFrXRMY EX2w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688340973; x=1690932973; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=g0JKGAaU0M6DI0blLqFva8m+lu2PaciyDl3AZ3Wwrs4=; b=VKdYObUc9G4n7RoNuD1Ni+/zD+pY0w1RB/YYctXqkblNxUpEOgV9wOHMNv7crz4tp3 q1VQaVIdd1XDcaS9ZY3S2n8j1q05nZ80XliLL2WDKtXhAmSuC0jGTS0Yhe2eJfvmsloQ IfkREMIft2kRvRG9M2sNjqUUUo8pVKdMu/f0p2F+0NQiJWlXPBTh5TvFgGCEpoOO+q/T bVLpXJr6IqwJAHiRP0pU0WiyVJq0lz27/+rRWxR+9+YboUHOB+iFxEqZ0EJ+txzLeBNn wSOLxtzfXit/eKc88kCdhTKpkmKvQSpkskankZSVlVzavlyr2re78L5IO3SBkWc35mMr DBZw== X-Gm-Message-State: ABy/qLZhytwKh49bzZvwIrrtzcSyv+WQ9CHdYY8kFyEHCJjIwKPZ/NyD ZBuBESbW5DcwSjdcDvZONbT2PQ== X-Google-Smtp-Source: APBJJlGKAMv5d0momhLUn/7kFg7s8f/AVnLnxPmuV/sMDnDdcuJdzwFpPyxb/3J8cSX8cO5f/j4yog== X-Received: by 2002:a17:90a:ea8a:b0:263:ac12:15cf with SMTP id h10-20020a17090aea8a00b00263ac1215cfmr4333157pjz.39.1688340972858; Sun, 02 Jul 2023 16:36:12 -0700 (PDT) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id 29-20020a17090a199d00b00263c6b44dd8sm651344pji.15.2023.07.02.16.36.12 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 02 Jul 2023 16:36:12 -0700 (PDT) Date: Sun, 2 Jul 2023 16:36:10 -0700 From: Stephen Hemminger To: aman.kumar@vvdntech.in Cc: Thomas Monjalon , hemant.agrawal@nxp.com, Hemant Agrawal , dev@dpdk.org, maxime.coquelin@redhat.com, david.marchand@redhat.com, Gagandeep Singh Subject: Re: [RFC PATCH 00/29] cover letter for net/qdma PMD Message-ID: <20230702163610.5aa696e8@hermes.local> In-Reply-To: References: <20220706075219.517046-1-aman.kumar@vvdntech.in> <6797649.18pcnM708K@thomas> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, 19 Jul 2022 22:52:20 +0530 aman.kumar@vvdntech.in wrote: > > >> > > >> QDMA is a very generic name and many vendors have IP for it. > > >> > > >> My suggestions is the qualify the specific driver with vendor name i.e. > > >> amd_qdma or xilinx_qdma or something similar. > > >> > > >> NXP also did the same dpaa2_qdma > > >> > > >> > > > @Thomas, @Hemant, > > > Thank you for highlights and suggestions regarding conflicting names. > > > We've discussed this internally and came up with below plan. > > > > > > For v22.11 DPDK, we would like to submit patches with below renames: > > > drivers/net/qdma -> drivers/net/t1 > > > drivers/net/qdma/qdma_*.c/h -> drivers/net/t1/t1_*.c/h > > > driver/net/qdma/qdma_access -> driver/net/t1/base > > > > Curious why "t1"? > > What is the meaning? > > The hardware is commerically named as the "T1 card". T1 represents first card of the telco accelerator series. > https://www.xilinx.com/publications/product-briefs/xilinx-t1-product-brief.pdf > The discussion around this driver stalled. Either hardware abandoned, renamed, or there was no interest. If you want to get this in a future DPDK release, please resubmit a new version addressing review comments.