From: Xiaoyun Li <xiaoyun.li@intel.com>
To: john.mcnamara@intel.com, beilei.xing@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, Xiaoyun Li <xiaoyun.li@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc: add recommended matching list in i40e guide
Date: Tue, 24 Jul 2018 14:49:28 +0800 [thread overview]
Message-ID: <1532414968-22983-1-git-send-email-xiaoyun.li@intel.com> (raw)
In-Reply-To: <1532327644-21715-1-git-send-email-xiaoyun.li@intel.com>
Add suggested kernel driver and firmware version for i40e PMD.
Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com>
---
doc/guides/nics/i40e.rst | 29 +++++++++++++++++++++++++++++
1 file changed, 29 insertions(+)
---
v2:
* Polish the title and section name
diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index d5b02c9..b8c1c1d 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -58,6 +58,35 @@ Prerequisites
- Upgrade the NVM/FW version following the `Intel® Ethernet NVM Update Tool Quick Usage Guide for Linux
<https://www-ssl.intel.com/content/www/us/en/embedded/products/networking/nvm-update-tool-quick-linux-usage-guide.html>`_ and `Intel® Ethernet NVM Update Tool: Quick Usage Guide for EFI <https://www.intel.com/content/www/us/en/embedded/products/networking/nvm-update-tool-quick-efi-usage-guide.html>`_ if needed.
+Recommended Matching List
+-------------------------
+
+It is highly recommended to upgrade the i40e kernel driver and firmware to
+avoid the compatibility issues with i40e PMD. Here is the suggested matching
+list which has been tested and verified.
+
+ +--------------+-----------------------+------------------+
+ | DPDK version | Kernel driver version | Firmware version |
+ +==============+=======================+==================+
+ | 18.05 | 2.4.6 | 6.01 |
+ +--------------+-----------------------+------------------+
+ | 18.02 | 2.4.3 | 6.01 |
+ +--------------+-----------------------+------------------+
+ | 17.11 | 2.1.26 | 6.01 |
+ +--------------+-----------------------+------------------+
+ | 17.08 | 2.0.19 | 6.01 |
+ +--------------+-----------------------+------------------+
+ | 17.05 | 1.5.23 | 5.05 |
+ +--------------+-----------------------+------------------+
+ | 17.02 | 1.5.23 | 5.05 |
+ +--------------+-----------------------+------------------+
+ | 16.11 | 1.5.23 | 5.05 |
+ +--------------+-----------------------+------------------+
+ | 16.07 | 1.4.25 | 5.04 |
+ +--------------+-----------------------+------------------+
+ | 16.04 | 1.4.25 | 5.02 |
+ +--------------+-----------------------+------------------+
+
Pre-Installation Configuration
------------------------------
--
2.7.4
next prev parent reply other threads:[~2018-07-24 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 6:34 [dpdk-dev] [PATCH] doc: add tested NICs " Xiaoyun Li
2018-07-24 5:26 ` Xing, Beilei
2018-07-24 6:45 ` Li, Xiaoyun
2018-07-24 6:49 ` Xiaoyun Li [this message]
2018-07-24 7:19 ` [dpdk-dev] [PATCH v3] doc: add i40e recommended matching list Xiaoyun Li
2018-07-24 7:28 ` Xing, Beilei
2018-07-30 1:11 ` Zhang, Qi Z
2018-07-24 7:32 ` Xu, Qian Q
2018-07-24 7:46 ` Li, Xiaoyun
2018-07-25 3:27 ` [dpdk-dev] [PATCH v4] " Xiaoyun Li
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=1532414968-22983-1-git-send-email-xiaoyun.li@intel.com \
--to=xiaoyun.li@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@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).