TI OMAP1 LCD framebuffer (omapfb)
The on-chip LCD controller found in Texas Instruments' first-generation OMAP1 mobile processors from the early 2000s, used to drive small displays on PDAs and early smartphones such as the Palm Tungsten E (2003-2005) and similar ARM-based handhelds.
recommendation
Worth keeping but its niche should be documented: although the OMAP1 hardware hasn't been sold in new products for roughly two decades and TI has long since exited the mobile SoC market, the driver is still receiving genuine upstream attention, including a stable-tagged bug fix and cleanup work in 2026. That ongoing maintenance, plus a small population of retro and embedded users, makes removal premature even though deployments today are low.
repository signals
sources
- git.kernel.org
The driver is for "OMAP frame buffer support" and depends on ARCH_OMAP1, indicating it targets older TI OMAP1-era boards rather than current TI display pipelines.
- lore.kernel.org
omapfb still receives real upstream fixes in 2026, including a bug fix tagged for stable backport.
- lore.kernel.org
omapfb also saw nontrivial cleanup in 2026, showing the driver is not abandoned in-tree.
- en.wikipedia.org
OMAP1 is an early-2000s TI mobile SoC family; TI later wound down OMAP smartphone/tablet efforts, supporting the view that this hardware family is long obsolete for new products.
- en.wikipedia.org
A concrete supported OMAP1-class product, the Palm Tungsten E, had a 2003-2005 lifespan, illustrating the vintage of devices this driver serves.
codex reasoning notes (technical)
Recommendation is keep-annotate, not deprecate/remove: lore evidence shows active maintenance rather than removal talk. The two lore URLs were obtained from MCP lore_file_timeline/lore_activity on drivers/video/fbdev/omap/omapfb_main.c. The kernel.org Kconfig URL is canonical recall, used to confirm this directory is the OMAP1-only fbdev driver. The two Wikipedia URLs were obtained by web search and used only for market-age/deployment context. Hardware appears long out of new-sales channels, but small legacy/retro/embedded use likely remains, so deployments_today=low and replacement_driver=null.