From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: [PATCH] doc: move firmware instructions in mlx5 guide
Date: Mon, 8 Jun 2026 14:05:31 +0200 [thread overview]
Message-ID: <20260608120531.1037367-1-thomas@monjalon.net> (raw)
Having firmware update instructions before firmware config
looks simpler to find than in compilation prerequisites.
A link is also added after listing minimum firmware versions.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/platform/mlx5.rst | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/doc/guides/platform/mlx5.rst b/doc/guides/platform/mlx5.rst
index 285d58be4f..0a8917530d 100644
--- a/doc/guides/platform/mlx5.rst
+++ b/doc/guides/platform/mlx5.rst
@@ -143,7 +143,7 @@ The following dependencies are not part of DPDK and must be installed separately
- BlueField-2: **24.28.1002** and above.
- BlueField-3: **32.36.3126** and above.
- New features may be added in more recent firmwares.
+ New features may be added in more recent :ref:`firmwares <mlx5_firmware_config>`.
Libraries and kernel modules can be provided either by the Linux distribution,
or by installing NVIDIA MLNX_OFED/EN which provides compatibility with older kernels.
@@ -171,11 +171,6 @@ It is possible to build rdma-core as static libraries starting with version 21::
ninja
ninja install
-The firmware can be updated with `mlxup
-<https://docs.nvidia.com/networking/display/mlxupfwutility>`_.
-The latest firmwares can be downloaded at
-https://network.nvidia.com/support/firmware/firmware-downloads/
-
NVIDIA MLNX_OFED/EN
^^^^^^^^^^^^^^^^^^^
@@ -490,6 +485,11 @@ Additional information can be found in the WinOF2 user manual.
Firmware Configuration
~~~~~~~~~~~~~~~~~~~~~~
+The firmware can be updated with `mlxup
+<https://docs.nvidia.com/networking/display/mlxupfwutility>`_
+after `downloading a new version
+<https://network.nvidia.com/support/firmware/firmware-downloads/>`_.
+
Firmware features can be configured as key/value pairs.
The command to set a value is::
--
2.54.0
next reply other threads:[~2026-06-08 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 12:05 Thomas Monjalon [this message]
2026-06-08 12:46 ` [PATCH] doc: move firmware instructions in mlx5 guide Dariusz Sosnowski
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=20260608120531.1037367-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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