test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: "Lu, PeipeiX" <peipeix.lu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Lu, PeipeiX" <peipeix.lu@intel.com>
Subject: Re: [dts] [PATCH V1] add fortville 25G Nics and its identifiers	supported by the framework
Date: Mon, 27 Mar 2017 01:19:36 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62D97DBA@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1489996075-31227-1-git-send-email-peipeix.lu@intel.com>

Thanks peipei, has merged in 25G support.

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of lu,peipei
> Sent: Monday, March 20, 2017 3:48 PM
> To: dts@dpdk.org
> Cc: Lu, PeipeiX <peipeix.lu@intel.com>
> Subject: [dts] [PATCH V1] add fortville 25G Nics and its identifiers
> supported by the framework
> 
> Signed-off-by: lu,peipei <peipeix.lu@intel.com>
> ---
>  framework/settings.py | 11 +++++++----
>  1 file changed, 7 insertions(+), 4 deletions(-)
> 
> diff --git a/framework/settings.py b/framework/settings.py
> index 86a29a3..9584cd1 100644
> --- a/framework/settings.py
> +++ b/framework/settings.py
> @@ -90,6 +90,7 @@ NICS = {
>      'ConnectX3': '15b3:1003',
>      'ConnectX4': '15b3:1013',
>      'boulderrapid': '8086:15d0',
> +    'fortville_25g': '8086:158b',
>  }
> 
>  DRIVERS = {
> @@ -109,7 +110,7 @@ DRIVERS = {
>      'sageville_vf': 'ixgbevf',
>      'sagepond': 'ixgbe',
>      'sagepond_vf': 'ixgbevf',
> -    'magnolia_park' : 'ixgbe',
> +    'magnolia_park': 'ixgbe',
>      'hartwell': 'igb',
>      '82545EM': 'igb',
>      '82540EM': 'igb',
> @@ -134,6 +135,7 @@ DRIVERS = {
>      'ConnectX3': 'mlx4_core',
>      'ConnectX4': 'mlx5_core',
>      'boulderrapid': 'fm10k',
> +    'fortville_25g': 'i40e',
>  }
> 
>  """
> @@ -209,13 +211,14 @@ DTS global error table
>  """
>  DTS_ERR_TBL = {
>      "GENERIC_ERR": 1,
> -    "DPDK_BUILD_ERR" : 2,
> -    "DUT_SETUP_ERR" : 3,
> -    "TESTER_SETUP_ERR" : 4,
> +    "DPDK_BUILD_ERR": 2,
> +    "DUT_SETUP_ERR": 3,
> +    "TESTER_SETUP_ERR": 4,
>      "SUITE_SETUP_ERR": 5,
>      "SUITE_EXECUTE_ERR": 6,
>  }
> 
> +
>  def get_nic_name(type):
>      """
>      strip nic code name by nic type
> --
> 1.9.3

  reply	other threads:[~2017-03-27  1:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20  7:47 lu,peipei
2017-03-27  1:19 ` Liu, Yong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-20  6:24 lu,peipei
2017-03-20  6: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=86228AFD5BCD8E4EBFD2B90117B5E81E62D97DBA@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=peipeix.lu@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).