From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: Rami Rosen <rami.rosen@huawei.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH] framework settings: adding Huawei Intelligent NIC PCI ID
Date: Sun, 24 Mar 2019 19:00:07 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BA45CC5@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5151E1D101B7B04382075E3B0EF69373E7F7D0@lhreml503-mbb>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Rami Rosen
> Sent: Sunday, March 24, 2019 7:18 AM
> To: dts@dpdk.org
> Subject: [dts] [PATCH] framework settings: adding Huawei Intelligent NIC PCI ID
>
> Huawei Intelligent PCIE PMD is targeted for DPDK 19.08:
> http://mails.dpdk.org/archives/web/2019-March/001050.html
> https://core.dpdk.org/roadmap/
>
> The patch below adds settings to support Huawei Intelligent PCIE ID in DTS, in
> order to enable us to run preliminary tests with latest DTS git code.
>
> Signed-off-by: Rami Rosen <rami.rosen@huawei.com>
> ---
> framework/settings.py | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/framework/settings.py b/framework/settings.py index
> 938a06c..732036d 100644
> --- a/framework/settings.py
> +++ b/framework/settings.py
> @@ -97,6 +97,7 @@ NICS = {
> 'fortville_25g': '8086:158b',
> 'cavium_a034': '177d:a034',
> 'cavium_0011': '177d:0011',
> + 'hi1822': '19e5:1822',
> }
>
> DRIVERS = {
> @@ -148,6 +149,7 @@ DRIVERS = {
> 'fortville_25g': 'i40e',
> 'cavium_a034': 'thunder-nicvf',
> 'cavium_0011': 'thunder-nicvf',
> + 'hi1822': 'hinic',
> }
>
> """
> --
> 1.8.3.1
prev parent reply other threads:[~2019-03-24 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 14:18 Rami Rosen
2019-03-24 19:00 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BA45CC5@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=rami.rosen@huawei.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).