Mellanox/NVIDIA ConnectX and Spectrum firmware-flash helper
Shared firmware-update support code used by NVIDIA (formerly Mellanox) ConnectX network adapters and Spectrum Ethernet switch ASICs, including the BlueField DPU line. It handles parsing and flashing the vendor's firmware image format on hardware that is widely deployed in modern datacenters and high-performance computing clusters.
recommendation
It should stay because the hardware it serves is still sold new in 2025 (ConnectX-7 adapters are listed in mass production by NVIDIA) and the code is actively maintained: a January 2025 fix raised the firmware image size limit to accommodate new BlueField-3 firmware, and a 2023 patch fixed a null-pointer dereference. With both the mlx5 and mlxsw drivers depending on it, this is core infrastructure for a major class of datacenter networking gear.
repository signals
sources
- git.kernel.org
Mainline received a January 2025 mlxfw fix removing a firmware image size limit because newer BlueField-3 firmware exceeded it, indicating current-hardware maintenance rather than obsolescence.
- git.kernel.org
Mainline also carried a 2023 mlxfw bug fix for a null-pointer dereference, showing the code still gets functional fixes.
- cateee.net
LKDDb lists CONFIG_MLXFW as a tristate module present across current kernel series, with module name mlxfw and definition in this directory.
- docs.nvidia.com
NVIDIA's ConnectX-7 adapter manual lists multiple adapter SKUs with lifecycle marked Mass Production, evidence that Mellanox/NVIDIA networking hardware using this firmware-update path is still sold in the mid-2020s.
codex reasoning notes (technical)
Local `sed`/`git grep` inspection showed this is a real shared firmware-flash driver component, not a pure helper library: it builds module `mlxfw` and is called by both `mlx5` and `mlxsw`. Local `git log` showed a substantive upstream touch on 2025-01-16. Kernel.org commit URLs were added by canonical recall from those locally observed hashes; LKDDb and NVIDIA docs URLs were obtained via web search. Separate web searches for lore removal/deprecation discussion did not surface an active removal thread. Because the code still gets upstream fixes and supports hardware families still in new datacenter deployments, removal/deprecation is not warranted.