From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ekadison@broadcom.com>
Received: from mail-gw3-out.broadcom.com (mail-gw3-out.broadcom.com
 [216.31.210.64]) by dpdk.org (Postfix) with ESMTP id 048D15952
 for <dts@dpdk.org>; Thu,  3 Sep 2015 00:35:59 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="5.17,457,1437462000"; d="scan'208,217";a="73957303"
Received: from irvexchcas06.broadcom.com (HELO
 IRVEXCHCAS06.corp.ad.broadcom.com) ([10.9.208.53])
 by mail-gw3-out.broadcom.com with ESMTP; 02 Sep 2015 15:58:20 -0700
Received: from IRVEXCHMB07.corp.ad.broadcom.com ([fe80::210e:9528:8c52:eb93])
 by IRVEXCHCAS06.corp.ad.broadcom.com ([::1]) with mapi id
 14.03.0235.001; Wed, 2 Sep 2015 15:35:57 -0700
From: Eric Kadison <ekadison@broadcom.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Thread-Topic: Adding support for a new NIC on DTS
Thread-Index: AdDlzlubNrQFUSIUQumZM9qZnXJpfg==
Date: Wed, 2 Sep 2015 22:35:56 +0000
Message-ID: <7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.9.208.64]
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [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 <dts.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dts>,
 <mailto:dts-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dts/>
List-Post: <mailto:dts@dpdk.org>
List-Help: <mailto:dts-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dts>,
 <mailto:dts-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Sep 2015 22:36:00 -0000

Hi everyone,
I'm trying to add support for a new NIC to DTS.  It is clear that the drive=
r needs to be identified in the settings.py file (by adding to the NICS dic=
t the device name (as the key) and PCI ID (as the value), and then adding t=
he kernel driver name (as value) to the same key in the DRIVERS dict).  Did=
 I miss anything?

After entering my DUT host computer information in crbs.py, and setting up =
execution.cfg, I expected some basic tests to run.  The hello_world test ra=
n successfully, but it does not bind my ports to the igb_uio driver.  So no=
 test that tries to run I/O runs.  In fact, it looks like the code in the p=
roject_dpdk.py file in set_target tries to bind the NIC to the kernel drive=
r.  Can anyone point me at a solution?

Test configuration use DTS from the master branch and DPDK 2.0.

Eric Kadison