From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.richardson@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id DC642AFD6
 for <dev@dpdk.org>; Mon, 23 Jun 2014 18:47:43 +0200 (CEST)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by orsmga101.jf.intel.com with ESMTP; 23 Jun 2014 09:47:39 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.01,531,1400050800"; d="scan'208";a="532777276"
Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155])
 by orsmga001.jf.intel.com with ESMTP; 23 Jun 2014 09:47:35 -0700
Received: from irsmsx103.ger.corp.intel.com ([169.254.3.31]) by
 IRSMSX102.ger.corp.intel.com ([169.254.2.76]) with mapi id 14.03.0123.003;
 Mon, 23 Jun 2014 17:47:33 +0100
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>, "Gooch, Stephen (Wind River)"
 <stephen.gooch@windriver.com>
Thread-Topic: PCIid 0x0436
Thread-Index: Ac+M2BSHfSWZOgdVSW+kKLbE5aKGHgBSfBzAADfmxuA=
Date: Mon, 23 Jun 2014 16:47:33 +0000
Message-ID: <59AF69C657FD0841A61C55336867B5B02CEDFA5D@IRSMSX103.ger.corp.intel.com>
References: <9205DC19ECCD944CA2FAC59508A772BABCF10CB9@ALA-MBA.corp.ad.wrs.com>
 <F35DEAC7BCE34641BA9FAC6BCA4A12E70A745AD8@SHSMSX104.ccr.corp.intel.com>
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A745AD8@SHSMSX104.ccr.corp.intel.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [163.33.239.180]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] PCIid 0x0436
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jun 2014 16:47:44 -0000

I've checked the Intel Communications Chipset 89xx Series (Cave Creek) data=
sheet [http://www.intel.ie/content/www/ie/en/intelligent-systems/crystal-fo=
rest-server/intel-communications-chipset-89xx-series-datasheet.html], and 0=
x0436 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 NI=
C drivers - compared to say, 0x0438, which does. Table 3-5 in the datasheet=
 indicates what PCI IDs correspond to what connection types. The previous t=
able, 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
>=20
> Hi Stephen
>=20
> It seems it hasn't been supported by standard Linux driver. We just follo=
w it.
> And what 0436 stands for? I am not quite sure about what it is.
>=20
> Regards,
> Helin
>=20
> -----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
>=20
> Hello,
>=20
> 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?
>=20
> Best Regards
> - Stephen