VIA Chrome9 integrated laptop camera controller
The webcam capture block built into VIA's Chrome9 integrated graphics chipsets from the late 2000s, paired with an OmniVision OV7670 sensor. Its main real-world home was the OLPC XO-1.5 laptop (a 2009 refresh of the One Laptop Per Child machine), and it was essentially never used outside that niche.
recommendation
Worth keeping but documenting its niche, because the hardware is firmly legacy (VIA Chrome9 plus OLPC XO-1.5 from around 2009) yet the code is not abandoned: it picked up genuine fixes in 2023, including a camera-sensor dependency fix and GPIO descriptor modernization, and there is no sign of any removal discussion upstream. A note pointing out that it is essentially an OLPC XO-1.5 driver would help future maintainers judge it accurately.
repository signals
sources
- cateee.net
LKDDb identifies CONFIG_VIDEO_VIA_CAMERA as the VIAFB camera controller driver for VIA Chrome9 chipsets, with the module still present through current kernel series.
- wiki.laptop.org
OLPC documents XO-1.5 as a 2009 hardware refresh built around VIA-based hardware, anchoring this driver to an old product generation rather than current hardware.
- wiki.laptop.org
OLPC documents XO-1.5 production boards and notes the Linux camera driver behavior on these systems, reinforcing that real deployments are tied to legacy XO-1.5 laptops.
- git.kernel.org
The driver received a substantive upstream fix in 2023 for camera sensor dependencies, showing it is not abandoned.
- git.kernel.org
The driver stack received GPIO descriptor modernization in 2023, another sign of ongoing maintenance rather than active removal.
codex reasoning notes (technical)
Shell inspection (`sed`) showed this is a real V4L2 platform driver and that Kconfig limits it to VIA Chrome9 hardware, only tested on OLPC XO-1.5 with OV7670 sensors. Local `git log` showed substantive touches in 2023-2024 plus treewide churn in 2026, with no sign of a removal series. Web search produced the LKDDb and OLPC wiki URLs above; a lore-focused web search returned no hits for removal/deprecation discussion, and direct lore fallback was unavailable here because MCP lore resources were absent and `lei` was not installed. Conclusion: hardware is clearly legacy and niche, but upstream still carries and occasionally fixes the driver, so annotate rather than deprecate/remove.