DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: dev@dpdk.org, "Chen,Bo" <box.c.chen@intel.com>, Chen@dpdk.org
Subject: Re: [dpdk-dev] [PATCH V1] doc: add testbed Intel platforms with Intel NICs
Date: Tue, 18 Feb 2020 18:52:06 +0800	[thread overview]
Message-ID: <20200218105206.GE104429@intel.com> (raw)
In-Reply-To: <20200218065158.63582-1-zhaoyan.chen@intel.com>

s/testbed/tested

On 02/18, Chen, Zhaoyan wrote:
>From: "Chen,Bo" <box.c.chen@intel.com>
>
>Add tested Intel platforms with Intel NICs to v20.02 release note.
>
>Signed-off-by: Chen,Bo <box.c.chen@intel.com>

Should be

Bo Chen <box.c.chen@intel.com>

>---
> doc/guides/rel_notes/release_20_02.rst | 106 +++++++++++++++++++++++++
> 1 file changed, 106 insertions(+)
>
>diff --git a/doc/guides/rel_notes/release_20_02.rst b/doc/guides/rel_notes/release_20_02.rst
>index 78dab7cfc3..0e69cc3f78 100644
>--- a/doc/guides/rel_notes/release_20_02.rst
>+++ b/doc/guides/rel_notes/release_20_02.rst
>@@ -325,3 +325,109 @@ Tested Platforms
>    This section is a comment. Do not overwrite or remove it.
>    Also, make sure to start the actual text at the margin.
>    =========================================================

Need on blank line here.

>+* Intel\ |reg| platforms with Intel\ |reg| NICs combinations
>+
>+  * CPU
>+
>+    * Intel\ |reg| Atom\ |trade| CPU C3758 @ 2.20GHz
>+    * Intel\ |reg| Atom\ |trade| CPU C3858 @ 2.00GHz
>+    * Intel\ |reg| Atom\ |trade| CPU C3958 @ 2.00GHz
>+    * Intel\ |reg| Xeon\ |reg| CPU D-1541 @ 2.10GHz
>+    * Intel\ |reg| Xeon\ |reg| CPU D-1553N @ 2.30GHz
>+    * Intel\ |reg| Xeon\ |reg| CPU E5-2680 0 @ 2.70GHz
>+    * Intel\ |reg| Xeon\ |reg| CPU E5-2680 v2 @ 2.80GHz
>+    * Intel\ |reg| Xeon\ |reg| CPU E5-2699 v3 @ 2.30GHz
>+    * Intel\ |reg| Xeon\ |reg| CPU E5-2699 v4 @ 2.20GHz
>+    * Intel\ |reg| Xeon\ |reg| Gold 6139 CPU @ 2.30GHz
>+    * Intel\ |reg| Xeon\ |reg| Gold 6252N CPU @ 2.30GHz
>+    * Intel\ |reg| Xeon\ |reg| Platinum 8180 CPU @ 2.50GHz
>+    * Intel\ |reg| Xeon\ |reg| Platinum 8280M CPU @ 2.70GHz
>+
>+  * OS:
>+
>+    * CentOS 7.7
>+    * CentOS 8.0
>+    * Fedora 31
>+    * FreeBSD 12.1
>+    * Red Hat Enterprise Linux Server release 8.0
>+    * Red Hat Enterprise Linux Server release 7.7
>+    * Suse15SP1
>+    * Ubuntu 14.04
>+    * Ubuntu 16.04
>+    * Ubuntu 16.10
>+    * Ubuntu 18.04
>+    * Ubuntu 19.04
>+
>+  * NICs:
>+
>+    * Intel\ |reg| Corporation Ethernet Controller E810-C for SFP (4x25G)
>+
>+      * Firmware version: 1.02 0x80002b69
>+      * Device id (pf): 8086:1593
>+      * Driver version: 0.12.34 (ice)
>+
>+    * Intel\ |reg| Corporation Ethernet Controller E810-C for SFP (2x100G)
>+
>+      * Firmware version: 1.02 0x80002b68
>+      * Device id (pf): 8086:1592
>+      * Driver version: 0.12.34 (ice)
>+
>+    * Intel\ |reg| 82599ES 10 Gigabit Ethernet Controller
>+
>+      * Firmware version: 0x61bf0001
>+      * Device id (pf/vf): 8086:10fb / 8086:10ed
>+      * Driver version: 5.6.1 (ixgbe)
>+
>+    * Intel\ |reg| Corporation Ethernet Connection X552/X557-AT 10GBASE-T
>+
>+      * Firmware version: 0x800003e7
>+      * Device id (pf/vf): 8086:15ad / 8086:15a8
>+      * Driver version: 5.1.0 (ixgbe)
>+
>+    * Intel\ |reg| Corporation Ethernet Controller 10G X550T
>+
>+      * Firmware version: 0x80000482
>+      * Device id (pf): 8086:1563
>+      * Driver version: 5.6.1 (ixgbe)
>+
>+    * Intel\ |reg| Ethernet Converged Network Adapter X710-DA4 (4x10G)
>+
>+      * Firmware version: 7.20 0x800079e8
>+      * Device id (pf/vf): 8086:1572 / 8086:154c
>+      * Driver version: 2.10.19.30 (i40e)
>+
>+    * Intel\ |reg| Corporation Ethernet Connection X722 for 10GbE SFP+ (4x10G)
>+
>+      * Firmware version: 4.11 0x80001def
>+      * Device id (pf/vf): 8086:37d0 / 8086:37cd
>+      * Driver version: 2.10.19.30 (i40e)
>+
>+    * Intel\ |reg| Corporation Ethernet Connection X722 for 10GBASE-T (2x10G)
>+
>+      * Firmware version: 4.10 0x80001a7a
>+      * Device id (pf/vf): 8086:37d2 / 8086:37cd
>+      * Driver version: 2.10.19.30 (i40e)
>+
>+    * Intel\ |reg| Ethernet Converged Network Adapter XXV710-DA2 (2x25G)
>+
>+      * Firmware version: 7.20 0x80007947
>+      * Device id (pf/vf): 8086:158b / 8086:154c
>+      * Driver version: 2.10.19.30 (i40e)
>+
>+    * Intel\ |reg| Ethernet Converged Network Adapter XL710-QDA2 (2X40G)
>+
>+      * Firmware version: 7.20 0x80007948
>+      * Device id (pf/vf): 8086:1583 / 8086:154c
>+      * Driver version: 2.10.19.30 (i40e)
>+
>+    * Intel\ |reg| Corporation I350 Gigabit Network Connection
>+
>+      * Firmware version: 1.63, 0x80000cbc
>+      * Device id (pf/vf): 8086:1521 / 8086:1520
>+      * Driver version: 5.4.0-k (igb)
>+
>+    * Intel\ |reg| Corporation I210 Gigabit Network Connection
>+
>+      * Firmware version: 3.25, 0x800006eb
>+      * Device id (pf): 8086:1533
>+      * Driver version: 5.4.0-k(igb)
>-- 
>2.17.1
>

Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>

Applied to dpdk-next-net-intel with above fixes, Thanks.

      reply	other threads:[~2020-02-18 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18  6:51 Chen, Zhaoyan
2020-02-18 10:52 ` Ye Xiaolong [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=20200218105206.GE104429@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=Chen@dpdk.org \
    --cc=box.c.chen@intel.com \
    --cc=dev@dpdk.org \
    --cc=zhaoyan.chen@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).