TI OMAP2/OMAP3 V4L2 video output driver
The video-output path on Texas Instruments OMAP2 and OMAP3 application processors, the ARM SoCs that powered a wave of smartphones, tablets, and embedded boards (such as the BeagleBoard) in the late 2000s and early 2010s. It exposes the chip's display overlays as a standard Linux video-output device so applications can push video frames to the screen.
recommendation
Worth keeping but documenting as a legacy niche. TI exited the OMAP smartphone and tablet business in 2012 and the chips were largely end-of-life by 2013, with major distributors now listing parts like the OMAP3503 as obsolete, so almost no new deployments exist. However, the code still receives occasional compatibility updates in 2024-2025 as the kernel's videobuf2 and V4L2 APIs evolve, and there is no upstream removal thread, so it is not a candidate for deletion yet — it just serves a shrinking pool of older BeagleBoard-class hardware.
repository signals
sources
- cateee.net
Upstream Kconfig still exposes this as CONFIG_VIDEO_OMAP2_VOUT, an OMAP2/OMAP3 V4L2-Display driver, so it remains buildable in current kernels.
- codebrowser.dev
Current upstream source is a real platform driver module (`omap_vout`) for TI OMAP video output, confirming the directory is driver code for legacy OMAP display hardware.
- digikey.com
At least one representative OMAP3 catalog MPU is marked obsolete/no longer manufactured by a major distributor, supporting that the hardware is not still sold new in 2025.
- en.wikipedia.org
OMAP as a family peaked in older mobile/embedded designs, TI exited the smartphone/tablet OMAP business in 2012, and later OMAP releases ended by 2013, supporting a legacy-only market position.
codex reasoning notes (technical)
Shell inspection of local source/Kconfig confirmed this is the OMAP2/3 V4L2 display driver. Shell `git -c safe.directory=... log` showed substantive non-mechanical touches in 2024-2025 (e.g. vb2/platform/V4L2 API updates), so the code is not abandoned enough to justify deprecate/remove. Attempted lore via `lei` failed because `lei` is unavailable; web lore searches did not surface an active removal thread, so I found no evidence to escalate to remove. URLs were obtained via web search results for LKDDb, codebrowser, DigiKey, and Wikipedia. Overall: legacy TI OMAP2/3 display-output hardware, not sold new, low present-day deployments, but still receiving occasional upstream compatibility maintenance, so `keep-annotate` fits better than deprecate/remove.