test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, HaiyangX" <haiyangx.zhao@intel.com>
Subject: Re: [dts] [PATCH V1] framework/settings: add iavf as CVL kernel vf	driver
Date: Fri, 19 Jun 2020 04:50:26 +0000	[thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BC5FB49@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1591861256-155849-1-git-send-email-haiyangx.zhao@intel.com>

Applied, thanks

-----Original Message-----
From: dts <dts-bounces@dpdk.org> On Behalf Of Haiyang Zhao
Sent: 2020年6月11日 15:41
To: dts@dpdk.org
Cc: Zhao, HaiyangX <haiyangx.zhao@intel.com>
Subject: [dts] [PATCH V1] framework/settings: add iavf as CVL kernel vf driver

*.in suite vf_to_vf_nic_bridge, need to bind CVL vf with kernel vf driver,
  so add iavf as CVL vf kernel driver.

Signed-off-by: Haiyang Zhao <haiyangx.zhao@intel.com>
---
 framework/settings.py | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/framework/settings.py b/framework/settings.py index d82b684..bb23077 100644
--- a/framework/settings.py
+++ b/framework/settings.py
@@ -105,6 +105,7 @@ NICS = {
     'cavium_a064': '177d:a064',
     'columbiaville_100g': '8086:1592',
     'columbiaville_25g': '8086:1593',
+    'columbiaville_vf': '8086:1889',
     'fastlinq_ql45000': '1077:1656',
     'fastlinq_ql45000_vf': '1077:1664',
     'fastlinq_ql41000': '1077:8070',
@@ -171,6 +172,7 @@ DRIVERS = {
     'cavium_a064': 'octeontx2-nicvf',
     'columbiaville_100g': 'ice',
     'columbiaville_25g': 'ice',
+    'columbiaville_vf': 'iavf',
     'fastlinq_ql45000': 'qede',
     'fastlinq_ql41000': 'qede',
     'fastlinq_ql45000_vf': 'qede',
--
1.8.3.1


      parent reply	other threads:[~2020-06-19  4:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11  7:40 Haiyang Zhao
2020-06-11  7:53 ` Zhao, HaiyangX
2020-06-19  4:50 ` Tu, Lijuan [this message]

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=8CE3E05A3F976642AAB0F4675D0AD20E0BC5FB49@SHSMSX101.ccr.corp.intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=haiyangx.zhao@intel.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).