From: Rami Rosen <rami.rosen@huawei.com>
To: "Lin, Xueqin" <xueqin.lin@intel.com>,
"Xu, Yanjie" <yanjie.xu@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Xu, Yanjie" <yanjie.xu@intel.com>
Subject: Re: [dts] [PATCH] dynamic add hardware requirement
Date: Thu, 18 Apr 2019 10:32:56 +0000 [thread overview]
Message-ID: <5151E1D101B7B04382075E3B0EF69373EC1C5F@lhreml503-mbs> (raw)
In-Reply-To: <0D300480287911409D9FF92C1FA2A3355B4D6BD1@SHSMSX104.ccr.corp.intel.com>
Hi,
>[Xueqin] The scope is too large, in /dpdk/drivers/net path, there are so many driver types, we may >test this suite on e1000, ixgbe, i40e, not try all especially not try on some not-intel NICs.
>"Any type NIC" is not make sense.
+1 on this.
Actually, as of now, DTS supports nics from four vendors: Intel, Cavium Networks, Mellanox and Huawei (see framework/setting.py)
Regards,
Rami
prev parent reply other threads:[~2019-04-18 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 13:51 xuyanjie
2019-04-18 8:18 ` Lin, Xueqin
2019-04-18 10:32 ` Rami Rosen [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=5151E1D101B7B04382075E3B0EF69373EC1C5F@lhreml503-mbs \
--to=rami.rosen@huawei.com \
--cc=dts@dpdk.org \
--cc=xueqin.lin@intel.com \
--cc=yanjie.xu@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).