Marvell Link Street 88E6xxx Ethernet switch chips
Marvell's Link Street 88E6xxx family of managed Ethernet switch chips, commonly embedded inside routers, industrial switches, and SoC-based networking gear. Parts like the 88E6390X, 88E6393X, and 88E6361 are still marketed in 2025 for smart/lightly-managed and industrial Ethernet applications, where they sit behind a host CPU and steer traffic across multiple ports.
recommendation
It should stay because the Link Street 88E6xxx family of managed switch chips is still actively sold by Marvell for industrial and embedded networking, and upstream development is healthy: a fresh net-next patch series in March 2026 adds new TCAM features, and there are no signs of removal or replacement on the netdev mailing list.
repository signals
sources
- lore.kernel.org
March 11, 2026 net-next patch series adds partial TCAM support to mv88e6xxx, showing active upstream feature development rather than retirement.
- marvell.com
Marvell's current switching catalog lists Link Street 6390, 6393X, and 6361 industrial products, indicating the family still had new-product relevance around 2025/2026.
- marvell.com
The 88E6390X product brief positions Link Street parts for smart/lightly managed and industrial Ethernet switches, matching ongoing embedded/industrial deployments.
codex reasoning notes (technical)
This is a real MDIO/DSA driver family, not a helper library. lore_file_timeline on drivers/net/dsa/mv88e6xxx/chip.c showed dense 2021-2026 activity and a fresh 2026-03-11 net-next feature series (source URL obtained from lore_file_timeline). A separate lore_regex scan for remove/deprecat/obsolete mentions with mv88e6xxx on netdev over 5y returned no hits, so there is no evident upstream removal push. Web search returned Marvell's live switching catalog and 88E6390X product brief (URLs obtained via web search), which show Link Street 6390/6393X family parts still marketed for industrial/managed-switch use. Because the directory covers a still-deployed embedded switch family with active upstream work and no obvious successor driver, the right call is keep.