From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-dev] [PATCH 3/3] doc: bump SDK support version for dpaa2
Date: Wed, 3 Apr 2019 14:23:44 +0000 [thread overview]
Message-ID: <20190403142357.17700-4-shreyansh.jain@nxp.com> (raw)
Message-ID: <20190403142344.XZAy2dMs7yVRvb5T2QT7EVszMiL6JvczEuSTEbV7-P0@z> (raw)
In-Reply-To: <20190403142357.17700-1-shreyansh.jain@nxp.com>
With the change in MC firmware, minimum supported version of
the Layerscape SDK too needs to be changed.
Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
---
doc/guides/nics/dpaa2.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/guides/nics/dpaa2.rst b/doc/guides/nics/dpaa2.rst
index 392ab0580..d74d8f899 100644
--- a/doc/guides/nics/dpaa2.rst
+++ b/doc/guides/nics/dpaa2.rst
@@ -421,8 +421,8 @@ See :doc:`../platform/dpaa2` for setup information
Currently supported by DPDK:
-- NXP SDK **18.09+**.
-- MC Firmware version **10.10.0** and higher.
+- NXP SDK **18.11+**.
+- MC Firmware version **10.14.0** and higher.
- Supported architectures: **arm64 LE**.
- Follow the DPDK :ref:`Getting Started Guide for Linux <linux_gsg>` to setup the basic DPDK environment.
--
2.19.1
next prev parent reply other threads:[~2019-04-03 14:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 14:23 [dpdk-dev] [PATCH 0/3] Update FSLMC bus firmware Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 1/3] bus/fslmc: cleanup unused firmware code Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` [dpdk-dev] [PATCH 2/3] drivers: update MC firmware version for FSLMC bus Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain
2019-04-03 14:23 ` Shreyansh Jain [this message]
2019-04-03 14:23 ` [dpdk-dev] [PATCH 3/3] doc: bump SDK support version for dpaa2 Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 1/3] bus/fslmc: cleanup unused firmware code Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 21:29 ` Ferruh Yigit
2019-04-04 21:29 ` Ferruh Yigit
2019-04-04 21:43 ` Thomas Monjalon
2019-04-04 21:43 ` Thomas Monjalon
2019-04-05 11:19 ` Shreyansh Jain
2019-04-05 11:19 ` Shreyansh Jain
2019-04-05 11:37 ` Ferruh Yigit
2019-04-05 11:37 ` Ferruh Yigit
2019-04-05 11:38 ` Shreyansh Jain
2019-04-05 11:38 ` Shreyansh Jain
2019-04-05 12:35 ` Thomas Monjalon
2019-04-05 12:35 ` Thomas Monjalon
2019-04-05 12:58 ` Shreyansh Jain
2019-04-05 12:58 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 2/3] drivers: update MC firmware version for FSLMC bus Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 7:23 ` [dpdk-dev] [PATCH v2 3/3] doc: bump SDK support version for dpaa2 Shreyansh Jain
2019-04-04 7:23 ` Shreyansh Jain
2019-04-04 21:08 ` [dpdk-dev] [PATCH v2 0/3] Update FSLMC bus firmware Thomas Monjalon
2019-04-04 21:08 ` Thomas Monjalon
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=20190403142357.17700-4-shreyansh.jain@nxp.com \
--to=shreyansh.jain@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).