From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org, Stephen Hurd <stephen.hurd@broadcom.com>,
Sony Chacko <sony.chacko@qlogic.com>,
Harish Patil <harish.patil@qlogic.com>,
Rasesh Mody <rasesh.mody@qlogic.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
John Daley <johndale@cisco.com>,
Nelson Escobar <neescoba@cisco.com>,
Jing Chen <jing.d.chen@intel.com>,
Helin Zhang <helin.zhang@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Huawei Xie <huawei.xie@intel.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>,
Yong Wang <yongwang@vmware.com>
Cc: ferruh.yigit@intel.com
Subject: [dpdk-dev] remove rte_pci_dev_ids.h
Date: Fri, 08 Jul 2016 16:31:01 +0200 [thread overview]
Message-ID: <27706267.i1CLxpQ5Lb@xps13> (raw)
Some drivers define the supported PCI IDs, others define them
in the common file rte_pci_dev_ids.h.
This situation brings some confusion in the layering design.
In order to clean up things, I've suggested a plan to remove
rte_pci_dev_ids.h:
http://dpdk.org/ml/archives/dev/2016-July/043596.html
I bring it here in a new thread to give more visibility.
There were 4 usages of this file:
- PMDs
- KNI ethtool (igb/ixgbe only)
- testpmd to use ixgbe bypass
- PCI autotest
This is the plan to get rid of them:
1/ remove need in PCI autotest (done: http://dpdk.org/commit/1dbba165)
2/ move PCI ids in bnx2x, bnxt, e1000, enic, fm10k, i40e, virtio, vmxnet3
3/ remove KNI ethtool (only igb/ixgbe support)
4/ remove bypass API or move it to ixgbe specific API
5/ move remaining PCI ids in igb and ixgbe PMDs
To make it short, please driver maintainers, move your PCI ids in your
drivers as soon as possible, in order to achieve step 2.
Thanks
reply other threads:[~2016-07-08 14:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27706267.i1CLxpQ5Lb@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harish.patil@qlogic.com \
--cc=helin.zhang@intel.com \
--cc=huawei.xie@intel.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.com \
--cc=rasesh.mody@qlogic.com \
--cc=sony.chacko@qlogic.com \
--cc=stephen.hurd@broadcom.com \
--cc=wenzhuo.lu@intel.com \
--cc=yongwang@vmware.com \
--cc=yuanhan.liu@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).