Samsung SXGBE 10G/2.5G/1G SoC Ethernet controller
A multi-speed (1G/2.5G/10G) Ethernet MAC block that Samsung integrated into certain ARM SoC designs, identified in device trees by the compatible string samsung,sxgbe-v2.0a. It targets embedded and SoC-class systems rather than discrete add-in NICs, and has only ever had this single Samsung IP variant as a known consumer.
recommendation
Worth keeping but documenting its niche, because the code is still being actively maintained with bug fixes flowing into stable trees as recently as December 2025, yet there is essentially no evidence of fresh product deployments or distro-visible users beyond the original 2014 Samsung SoC binding. In practice it serves a small, legacy embedded audience, so it should remain in tree but be flagged as low-footprint hardware support.
repository signals
sources
- lore.kernel.org
The driver was still receiving upstream-stable fixes in December 2025, including a NULL-dereference fix in `sxgbe_rx()`.
- cateee.net
LKDDb identifies this as `CONFIG_SXGBE_ETH`, a Samsung platform Ethernet driver with one DT match (`samsung,sxgbe-v2.0a`) and no broad PCI/USB device coverage.
- spinics.net
The original DT binding series describes SXGBE as a Samsung 10G Ethernet block with compatible string `samsung,sxgbe-v2.0a`, indicating narrow SoC-specific deployment.
codex reasoning notes (technical)
Local `rg`/`sed` inspection showed a single OF match (`samsung,sxgbe-v2.0a`) and module description `Samsung 10G/2.5G/1G Ethernet PLATFORM driver`, so this is a real Samsung SoC platform NIC driver rather than a generic bus device. `lore_file_timeline` on `sxgbe_main.c` showed ongoing activity through 2025, dominated by fixes and multiple stable backports, and no removal-thread evidence surfaced in the lore queries attempted; that argues against deprecate/remove. Web search for the exact compatible string mainly surfaced LKDDb and the 2014 binding post, with no current product or distro-facing ecosystem evidence, so present-day use looks niche/legacy embedded rather than new mainstream deployments. Result: keep the driver, but annotate it as low-deployment legacy Samsung SoC IP with limited contemporary hardware footprint. URLs were obtained via `lore_file_timeline` and web search; local source details came from shell inspection.