DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pei, Yulong" <yulong.pei@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
	"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
	"Xu, Qian Q" <qian.q.xu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add tested platforms and nics and OSes
Date: Sat, 4 Feb 2017 03:57:47 +0000	[thread overview]
Message-ID: <188971FCDA171749BED5DA74ABF3E6F03B68950B@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1485160698-5252-1-git-send-email-yulong.pei@intel.com>

Hi Thomas,

Did you notice this patch ? do you have any comments ?

Thanks
Yulong Pei

-----Original Message-----
From: Pei, Yulong 
Sent: Monday, January 23, 2017 4:38 PM
To: dev@dpdk.org
Cc: Mcnamara, John <john.mcnamara@intel.com>; thomas.monjalon@6wind.com; Pei, Yulong <yulong.pei@intel.com>
Subject: [PATCH] doc: add tested platforms and nics and OSes

Add tested platforms and nics and OSes to the release notes.

Signed-off-by: Yulong Pei <yulong.pei@intel.com>
---
 doc/guides/rel_notes/release_17_02.rst | 103 +++++++++++++++++++++++++++++++++
 1 file changed, 103 insertions(+)

diff --git a/doc/guides/rel_notes/release_17_02.rst b/doc/guides/rel_notes/release_17_02.rst
index 0ecd720..f62dea1 100644
--- a/doc/guides/rel_notes/release_17_02.rst
+++ b/doc/guides/rel_notes/release_17_02.rst
@@ -368,6 +368,57 @@ Tested Platforms
    Also, make sure to start the actual text at the margin.
    =========================================================
 
+#. SuperMicro 1U
+
+   - BIOS: 1.0c
+   - Processor: Intel(R) Atom(TM) CPU C2758 @ 2.40GHz
+
+#. SuperMicro 1U
+
+   - BIOS: 1.0a
+   - Processor: Intel(R) Xeon(R) CPU D-1540 @ 2.00GHz
+   - Onboard NIC: Intel(R) X552/X557-AT (2x10G)
+
+     - Firmware-version: 0x800001cf
+     - Device ID (PF/VF): 8086:15ad /8086:15a8
+
+   - kernel driver version: 4.2.5 (ixgbe)
+
+#. SuperMicro 2U
+
+   - BIOS: 1.0a
+   - Processor: Intel(R) Xeon(R) CPU E5-4667 v3 @ 2.00GHz
+
+#. Intel(R) Server board S2600GZ
+
+   - BIOS: SE5C600.86B.02.02.0002.122320131210
+   - Processor: Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz
+
+#. Intel(R) Server board S2600CWT
+
+   - BIOS: SE5C610.86B.01.01.0009.060120151350
+   - Processor: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
+
+#. Intel(R) Server board S2600WTT
+
+   - BIOS: SE5C610.86B.01.01.0005.101720141054
+   - Processor: Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
+
+#. Intel(R) Server board S2600WTT
+
+   - BIOS: SE5C610.86B.11.01.0044.090120151156
+   - Processor: Intel(R) Xeon(R) CPU E5-2695 v4 @ 2.10GHz
+
+#. Intel Corporation S2600GZ
+
+   - BIOS: SE5C600.86B.01.06.0002.110120121539
+   - Processor: Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz
+
+#. Intel Corporation S2600CO
+
+   - BIOS: SE5C600.86B.02.02.0002.122320131210
+   - Processor: Intel(R) Xeon(R) CPU E5-2658 v2 @ 2.40GHz
+
 
 Tested NICs
 -----------
@@ -385,6 +436,48 @@ Tested NICs
    Also, make sure to start the actual text at the margin.
    =========================================================
 
+#. Intel(R) 82599ES 10 Gigabit Ethernet Controller
+
+   - Firmware version: 0x61bf0001
+   - Device id (pf/vf): 8086:10fb / 8086:10ed
+   - Driver version: 4.0.1-k (ixgbe)
+
+#. Intel(R) Corporation Ethernet Connection X552/X557-AT 10GBASE-T
+
+   - Firmware version: 0x800001cf
+   - Device id (pf/vf): 8086:15ad / 8086:15a8
+   - Driver version: 4.2.5 (ixgbe)
+
+#. Intel(R) Ethernet Converged Network Adapter X710-DA4 (4x10G)
+
+   - Firmware version: 5.05
+   - Device id (pf/vf): 8086:1572 / 8086:154c
+   - Driver version: 1.5.23 (i40e)
+
+#. Intel(R) Ethernet Converged Network Adapter X710-DA2 (2x10G)
+
+   - Firmware version: 5.05
+   - Device id (pf/vf): 8086:1572 / 8086:154c
+   - Driver version: 1.5.23 (i40e)
+
+#. Intel(R) Ethernet Converged Network Adapter XL710-QDA1 (1x40G)
+
+   - Firmware version: 5.05
+   - Device id (pf/vf): 8086:1584 / 8086:154c
+   - Driver version: 1.5.23 (i40e)
+
+#. Intel(R) Ethernet Converged Network Adapter XL710-QDA2 (2X40G)
+
+   - Firmware version: 5.05
+   - Device id (pf/vf): 8086:1583 / 8086:154c
+   - Driver version: 1.5.23 (i40e)
+
+#. Intel(R) Corporation I350 Gigabit Network Connection
+
+   - Firmware version: 1.48, 0x800006e7
+   - Device id (pf/vf): 8086:1521 / 8086:1520
+   - Driver version: 5.2.13-k (igb)
+
 
 Tested OSes
 -----------
@@ -405,3 +498,13 @@ Tested OSes
    This section is a comment. do not overwrite or remove it.
    Also, make sure to start the actual text at the margin.
    =========================================================
+
+* CentOS 7.2
+* Fedora 25
+* FreeBSD 11
+* Red Hat Enterprise Linux Server release 7.3
+* SUSE Enterprise Linux 12
+* Wind River Linux 8
+* Ubuntu 16.04
+* Ubuntu 16.10
+
-- 
2.1.0

       reply	other threads:[~2017-02-04  3:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1485160698-5252-1-git-send-email-yulong.pei@intel.com>
2017-02-04  3:57 ` Pei, Yulong [this message]
2017-02-07 10:30   ` Thomas Monjalon
2017-02-09  8:42   ` Nélio Laranjeiro
2017-02-13 18:06     ` Thomas Monjalon
2017-02-08 17:53 ` Mcnamara, John
2017-02-14  0:31 ` Mcnamara, John

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=188971FCDA171749BED5DA74ABF3E6F03B68950B@shsmsx102.ccr.corp.intel.com \
    --to=yulong.pei@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=thomas.monjalon@6wind.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).