* [dpdk-dev] PCIid 0x0436
@ 2014-06-20 22:40 Gooch, Stephen
2014-06-22 14:00 ` Zhang, Helin
0 siblings, 1 reply; 4+ messages in thread
From: Gooch, Stephen @ 2014-06-20 22:40 UTC (permalink / raw)
To: dev
Hello,
Cave Creek has PCI id of 0x0436 for port0 and 0x0438 for port1. However only 0x0438 is listed in rte_pci_dev_ids.h. Why is 0x0436 not listed?
Best Regards
- Stephen
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] PCIid 0x0436
2014-06-20 22:40 [dpdk-dev] PCIid 0x0436 Gooch, Stephen
@ 2014-06-22 14:00 ` Zhang, Helin
2014-06-23 16:47 ` Richardson, Bruce
0 siblings, 1 reply; 4+ messages in thread
From: Zhang, Helin @ 2014-06-22 14:00 UTC (permalink / raw)
To: Gooch, Stephen (Wind River); +Cc: dev
Hi Stephen
It seems it hasn't been supported by standard Linux driver. We just follow it.
And what 0436 stands for? I am not quite sure about what it is.
Regards,
Helin
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gooch, Stephen
Sent: Saturday, June 21, 2014 6:40 AM
To: dev@dpdk.org
Subject: [dpdk-dev] PCIid 0x0436
Hello,
Cave Creek has PCI id of 0x0436 for port0 and 0x0438 for port1. However only 0x0438 is listed in rte_pci_dev_ids.h. Why is 0x0436 not listed?
Best Regards
- Stephen
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] PCIid 0x0436
2014-06-22 14:00 ` Zhang, Helin
@ 2014-06-23 16:47 ` Richardson, Bruce
0 siblings, 0 replies; 4+ messages in thread
From: Richardson, Bruce @ 2014-06-23 16:47 UTC (permalink / raw)
To: Zhang, Helin, Gooch, Stephen (Wind River); +Cc: dev
I've checked the Intel Communications Chipset 89xx Series (Cave Creek) datasheet [http://www.intel.ie/content/www/ie/en/intelligent-systems/crystal-forest-server/intel-communications-chipset-89xx-series-datasheet.html], and 0x0436 is indeed one of the possible PCI IDs used by that product. However, the datasheet explicitly says that it does not need to be handled by the NIC drivers - compared to say, 0x0438, which does. Table 3-5 in the datasheet indicates what PCI IDs correspond to what connection types. The previous table, Table 3-4, was more confusing and seemed to indicate that the PCI ID was based on the Port number, but Table 3-5 clarifies things.
Regards,
/Bruce
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhang, Helin
> Sent: Sunday, June 22, 2014 7:00 AM
> To: Gooch, Stephen (Wind River)
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] PCIid 0x0436
>
> Hi Stephen
>
> It seems it hasn't been supported by standard Linux driver. We just follow it.
> And what 0436 stands for? I am not quite sure about what it is.
>
> Regards,
> Helin
>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Gooch, Stephen
> Sent: Saturday, June 21, 2014 6:40 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] PCIid 0x0436
>
> Hello,
>
> Cave Creek has PCI id of 0x0436 for port0 and 0x0438 for port1. However only
> 0x0438 is listed in rte_pci_dev_ids.h. Why is 0x0436 not listed?
>
> Best Regards
> - Stephen
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-dev] PCIid 0x0436
@ 2014-06-20 23:32 Gooch, Stephen
0 siblings, 0 replies; 4+ messages in thread
From: Gooch, Stephen @ 2014-06-20 23:32 UTC (permalink / raw)
To: dev
Thanks for the answer off line. 0x0436 is the DID not handled by the OS network driver. I incorrectly read the Cave Creek document.
- Stephen
From: Gooch, Stephen
Sent: Friday, June 20, 2014 3:40 PM
To: dev@dpdk.org
Subject: PCIid 0x0436
Hello,
Cave Creek has PCI id of 0x0436 for port0 and 0x0438 for port1. However only 0x0438 is listed in rte_pci_dev_ids.h. Why is 0x0436 not listed?
Best Regards
- Stephen
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2014-06-23 16:47 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-20 22:40 [dpdk-dev] PCIid 0x0436 Gooch, Stephen
2014-06-22 14:00 ` Zhang, Helin
2014-06-23 16:47 ` Richardson, Bruce
2014-06-20 23:32 Gooch, Stephen
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).