From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Sean Hope (shope)" <shope@cisco.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] ethdev: replacement for rte_pci_dev_ids.h?
Date: Thu, 07 Apr 2016 21:16:22 +0200 [thread overview]
Message-ID: <1515516.pAGpqdKvpf@xps13> (raw)
In-Reply-To: <D32C1AF4.33F217%shope@cisco.com>
2016-04-07 18:10, Sean Hope:
> Hello,
>
> I see that rte_pci_dev_ids.h has been removed.
No it has not been removed (yet):
http://dpdk.org/browse/dpdk/tree/lib/librte_eal/common/include/rte_pci_dev_ids.h
> We are using it on our product to get supported device ids.
>
> I understand the desire to move that data out of a central place and into
> each driver. Any chance that instead of living in a .c file, that each
> driver could hold it in a .h file so that it could be easily consumed by
> an external program?
Yes there is a plan to move the PCI ids in the drivers but
we need to make a tool to retrieve the ids from the ELF files.
Why do you want to get them from a .h file?
next prev parent reply other threads:[~2016-04-07 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 18:10 Sean Hope (shope)
2016-04-07 19:16 ` Thomas Monjalon [this message]
2016-04-08 3:27 ` Sean Hope (shope)
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=1515516.pAGpqdKvpf@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=shope@cisco.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).