From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 4907B5A30 for ; Sun, 6 Sep 2015 02:48:19 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP; 05 Sep 2015 17:48:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,476,1437462000"; d="scan'208";a="783631840" Received: from pgsmsx102.gar.corp.intel.com ([10.221.44.80]) by fmsmga001.fm.intel.com with ESMTP; 05 Sep 2015 17:48:17 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.110.15) by PGSMSX102.gar.corp.intel.com (10.221.44.80) with Microsoft SMTP Server (TLS) id 14.3.224.2; Sun, 6 Sep 2015 08:48:16 +0800 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.248]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.210]) with mapi id 14.03.0224.002; Sun, 6 Sep 2015 08:48:15 +0800 From: "Liu, Yong" To: Eric Kadison , "dts@dpdk.org" Thread-Topic: Adding support for a new NIC on DTS Thread-Index: AdDlzlubNrQFUSIUQumZM9qZnXJpfgCbjvGA Date: Sun, 6 Sep 2015 00:48:14 +0000 Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10EE1BF3@SHSMSX103.ccr.corp.intel.com> References: <7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com> In-Reply-To: <7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] Adding support for a new NIC on DTS X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Sep 2015 00:48:19 -0000 Hi Eric, Can you show your settings in execution.cfg? By default NIC port type is "c= fg" which mean DTS will only load ports which defined in conf/ports.cfg. Here is one sample for port configuration file. Setting "pci" mean the pci = address of DUT port, "peer" mean the opposite test port pci address. [root@dpdk-test38 dts]# cat conf/ports.cfg [DUT IP] ports=3D pci=3D87:00.0,peer=3D07:00.0; pci=3D87:00.1,peer=3D07:00.1; > -----Original Message----- > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Eric Kadison > Sent: Thursday, September 03, 2015 6:36 AM > To: dts@dpdk.org > Subject: [dts] Adding support for a new NIC on DTS >=20 > Hi everyone, > I'm trying to add support for a new NIC to DTS. It is clear that the > driver needs to be identified in the settings.py file (by adding to the > NICS dict the device name (as the key) and PCI ID (as the value), and the= n > adding the kernel driver name (as value) to the same key in the DRIVERS > dict). Did I miss anything? >=20 > After entering my DUT host computer information in crbs.py, and setting u= p > execution.cfg, I expected some basic tests to run. The hello_world test > ran successfully, but it does not bind my ports to the igb_uio driver. S= o > no test that tries to run I/O runs. In fact, it looks like the code in > the project_dpdk.py file in set_target tries to bind the NIC to the kerne= l > driver. Can anyone point me at a solution? >=20 > Test configuration use DTS from the master branch and DPDK 2.0. >=20 > Eric Kadison