From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
"Gooch, Stephen (Wind River)" <stephen.gooch@windriver.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] PCIid 0x0436
Date: Mon, 23 Jun 2014 16:47:33 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B02CEDFA5D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A745AD8@SHSMSX104.ccr.corp.intel.com>
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
next prev parent reply other threads:[~2014-06-23 16:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 22:40 Gooch, Stephen
2014-06-22 14:00 ` Zhang, Helin
2014-06-23 16:47 ` Richardson, Bruce [this message]
2014-06-20 23:32 Gooch, Stephen
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=59AF69C657FD0841A61C55336867B5B02CEDFA5D@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=stephen.gooch@windriver.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).