Cavium/Marvell ThunderX Ethernet NIC, BGX, and RGX controllers
On-chip Ethernet networking (the NIC physical and virtual functions plus the BGX and RGX MAC blocks) built into Cavium's ThunderX family of 64-bit Arm server processors, used in data-center and HPC servers from roughly the mid-2010s. ThunderX2 saw real production use, including in Microsoft Azure development infrastructure around 2019.
recommendation
Worth keeping but documenting its niche: Marvell publicly shifted away from the ThunderX line in August 2020 and the chips are no longer sold for new builds, yet the code is still actively maintained upstream, with patches landing in 2025 and stable backports as recent as September 2025. That maintenance pattern points to real installed-base servers still running these CPUs, so removing the driver would strand them while keeping it costs little.
repository signals
sources
- lore.kernel.org
The driver family still receives upstream maintenance in 2026; a netdev/linux-pci patch updated thunder_bgx to use pcim_alloc_irq_vectors().
- lore.kernel.org
Thunder BGX fixes were backported to stable in September 2025, indicating maintained deployed systems rather than abandonware.
- marvell.com
Marvell said in August 2020 it had changed its strategy for ThunderX, describing ThunderX as an older server-processor product line and pivoting toward custom Arm solutions.
- marvell.com
ThunderX2 had real production deployments historically, including Microsoft Azure internal servers in 2019.
- cateee.net
LKDDb shows the Thunder BGX driver is still present in current kernels and ties it to Cavium ThunderX PCI device IDs.
codex reasoning notes (technical)
Real driver directory: local shell inspection found PCI module drivers nicpf/nicvf/thunder_bgx/thunder_xcv under this path. lore_activity MCP on thunder_bgx.c returned 2026 upstream maintenance and 2025 stable backports; no removal evidence surfaced, and lore_file_timeline on the directory path returned no direct hits, so I treated that as a path-match blind spot rather than inactivity. Web search/open on Marvell pages showed ThunderX was a historical server line with a 2020 strategy change, while a 2019 Marvell release showed genuine deployment history. Web search on LKDDb confirmed current kernel presence and device IDs. Conclusion: hardware is commercially obsolete for new 2025 purchases, but there is still enough maintenance and installed-base evidence to keep the driver with obsolescence annotation rather than deprecate/remove.