drivers/net/ethernet/cavium/octeon

Cavium Octeon CN5xxx/CN6xxx management-port Ethernet

The dedicated low-speed management Ethernet port found on Cavium's Octeon MIPS-based system-on-chip processors (the CN5xxx and CN6xxx generations), which were widely used through the 2000s and 2010s in networking appliances, routers, and security gateways. The port is typically used for out-of-band administration rather than data-plane traffic.

keep-annotate conf=0.80 deploy=low replacement=none subsystem=net category=networking-ethernet
80%

recommendation

Worth keeping but flagging as legacy because the hardware targets an older Cavium MIPS SoC family that is no longer sold for new designs, yet the code is clearly not abandoned: maintainers were still modernizing it in 2024 (tasklet and platform_driver API updates) and as recently as 2025 (conversion to the new hardware timestamp callbacks). Existing embedded deployments still benefit from upstream presence, so removal would be premature, but the driver should be documented as serving a shrinking installed base.

repository signals

2 files
1,558 source lines
10 commits, 5y
+42 / −44 lines added / removed, 5y
8 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 10 total · active in 10/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 0 commits · +0 −0 2021-06: 0 commits · +0 −0 2021-07: 1 commit · +1 −1 2021-08: 0 commits · +0 −0 2021-09: 0 commits · +0 −0 2021-10: 1 commit · +1 −1 2021-11: 1 commit · +1 −1 2021-12: 1 commit · +0 −3 2022-01: 0 commits · +0 −0 2022-02: 0 commits · +0 −0 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 0 commits · +0 −0 2022-07: 0 commits · +0 −0 2022-08: 1 commit · +1 −1 2022-09: 0 commits · +0 −0 2022-10: 1 commit · +2 −2 2022-11: 0 commits · +0 −0 2022-12: 0 commits · +0 −0 2023-01: 0 commits · +0 −0 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 0 commits · +0 −0 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 1 commit · +2 −3 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 0 commits · +0 −0 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 1 commit · +1 −1 2024-06: 0 commits · +0 −0 2024-07: 0 commits · +0 −0 2024-08: 0 commits · +0 −0 2024-09: 0 commits · +0 −0 2024-10: 1 commit · +1 −1 2024-11: 0 commits · +0 −0 2024-12: 0 commits · +0 −0 2025-01: 0 commits · +0 −0 2025-02: 0 commits · +0 −0 2025-03: 0 commits · +0 −0 2025-04: 0 commits · +0 −0 2025-05: 0 commits · +0 −0 2025-06: 0 commits · +0 −0 2025-07: 0 commits · +0 −0 2025-08: 0 commits · +0 −0 2025-09: 0 commits · +0 −0 2025-10: 0 commits · +0 −0 2025-11: 1 commit · +32 −30 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 0 commits · +0 −0 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    Recent substantive upstream maintenance exists: 2025 net-next work converted octeon_mgmt to ndo_hwtstamp callbacks.

  2. lore.kernel.org

    The driver was still being mechanically modernized in 2024 via tasklet API conversion, indicating it remains build- and runtime-relevant.

  3. lore.kernel.org

    The file was included in 2024 platform_driver remove-callback API churn; this is maintenance activity, not removal.

  4. cateee.net

    LKDDb maps the driver to OCTEON_MGMT_ETHERNET on Cavium Octeon SoCs, matching the CN5xxx/CN6xxx management-port niche.

  5. en.wikipedia.org

    Octeon is an older Cavium MIPS SoC family, supporting the conclusion that this driver targets legacy embedded/networking hardware rather than a 2025 new-design platform.

codex reasoning notes (technical)

`octeon_mgmt.c` is a real platform net driver for Octeon management ports. `lore_file_timeline` on the file showed nontrivial 2024-2025 touches, including a 2025 hwtstamp callback conversion and 2024 API modernization, so the driver is not abandoned and available lore evidence does not show an active removal series. Hardware scope is narrow and old: local Kconfig names CN5xxx/CN6xxx only; supporting URLs were obtained via `lore_file_timeline` (three lore links) plus canonical recall of stable reference pages (LKDDb and Wikipedia). Conclusion: keep upstream for legacy users, but annotate as old/legacy hardware with low current deployment expectations.