Samsung S5P/Exynos4 G2D 2D graphics accelerator
A 2D graphics acceleration block built into Samsung's S5PV210 and Exynos 4 (4210/4212/4412) mobile SoCs from roughly 2010-2012, used to offload bitmap blits, fills, and rotations on phones and tablets like early Galaxy devices and ODROID-class developer boards.
recommendation
Worth keeping but documenting its niche, because the SoCs it targets are 2011-2012 vintage and have no current commercial relevance, yet the code is still receiving patches into 2025 and is actively used by the postmarketOS community to keep old Galaxy phones and ODROID boards running mainline Linux. There is no upstream removal discussion, so the sensible path is to flag it as legacy/hobbyist hardware rather than drop it.
repository signals
sources
- spinics.net
Public patch traffic still touched s5p-g2d in 2025, indicating ongoing upstream maintenance rather than abandonment/removal.
- wiki.postmarketos.org
Exynos 4210/4212/4412 are 2011-2012-era chips still seeing niche mainline/postmarketOS use on old phones/tablets and a few dev boards.
- en.wikichip.org
Exynos 4210 was introduced in 2011, supporting the conclusion that the covered hardware family is long past new mainstream deployment.
- cateee.net
CONFIG_VIDEO_SAMSUNG_S5P_G2D remains present in current kernels, so the driver is still shipped upstream.
codex reasoning notes (technical)
Local exec_command inspection shows this is a real platform driver with DT matches for samsung,s5pv210-g2d and samsung,exynos4212-g2d, i.e. old S5PV210/Exynos4-era 2D accelerators. Local git log shows substantive touches through 2025-10-17 and additional 2026 treewide churn, so it is not dormant enough for deprecate/remove. Web search for lore-style mailing-list evidence found 2025 patch traffic on spinics for s5p-g2d and no visible removal/deprecation thread; that argues against removal. Web search also found postmarketOS deployment evidence for surviving hobbyist/mainlining use on legacy Galaxy/ODROID-class devices, but those SoCs date to 2011-2012 (WikiChip), so present-day deployment is low and almost entirely legacy/community. URLs were obtained via web search; code/compatibility evidence came from local exec_command reads.