From: Eric Kadison <ekadison@broadcom.com>
To: "dts@dpdk.org" <dts@dpdk.org>
Subject: [dts] Adding support for a new NIC on DTS
Date: Wed, 2 Sep 2015 22:35:56 +0000 [thread overview]
Message-ID: <7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com> (raw)
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 then adding the 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 ran 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 project_dpdk.py file in set_target tries to bind the NIC to the kernel driver. Can anyone point me at a solution?
Test configuration use DTS from the master branch and DPDK 2.0.
Eric Kadison
next reply other threads:[~2015-09-02 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 22:35 Eric Kadison [this message]
2015-09-06 0:48 ` Liu, Yong
2015-09-10 4:25 ` Eric Kadison
2015-09-10 5:36 ` Xu, Qian Q
2015-09-10 5:57 ` Liu, Yong
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=7C99D44D787C8F4B9DC7D9BF9E66805410000729@IRVEXCHMB07.corp.ad.broadcom.com \
--to=ekadison@broadcom.com \
--cc=dts@dpdk.org \
/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).