Raspberry Pi VideoCore VCHIQ messaging interface
The message-passing channel that lets the ARM Linux side of a Raspberry Pi talk to the Broadcom VideoCore firmware running on the GPU side of BCM2835/BCM2836-class SoCs. It carries multimedia and firmware service traffic (camera, codecs, mailbox-style requests) that Pi userspace tools rely on, and has been part of the Pi platform since the original Model B in 2012.
recommendation
Worth keeping but worth a comment in the tree noting its niche, because while the code itself has seen no substantive changes in roughly five years beyond mechanical treewide touch-ups, the hardware it serves is very much alive: Raspberry Pi 5 and Compute Module 5 are current 2025 products with committed production through 2036, and Raspberry Pi OS still ships VideoCore firmware tooling that depends on this channel. There is no drop-in replacement for the firmware interface, so removal would break a large active install base.
repository signals
sources
- cateee.net
LKDDb shows CONFIG_BCM2835_VCHIQ is present in current kernels under drivers/platform/raspberrypi, with brcm,bcm2835-vchiq and brcm,bcm2836-vchiq device matches.
- raspberrypi.com
Raspberry Pi 5 is a current product, available now, and its product page states production will continue until at least January 2036.
- raspberrypi.com
Compute Module 5 is available now, showing the Raspberry Pi VideoCore-era platform family is still sold for new embedded deployments.
- raspberrypi.com
Current Raspberry Pi documentation still exposes VideoCore firmware-facing tooling, indicating ongoing firmware-mediated deployments rather than a dead legacy stack.
codex reasoning notes (technical)
Local code inspection via exec_command showed this is the BCM2835 VCHIQ kernel/firmware messaging interface used by Raspberry Pi multimedia and firmware services, not a helper-only directory. Local git log via exec_command showed only a recent mechanical treewide touch and no substantive 5-year activity. Lore search attempts found no obvious removal discussion or active patch flow. URLs were obtained via web search: LKDDb for current upstream presence; Raspberry Pi 5 and Compute Module 5 product pages for present-day hardware availability; Raspberry Pi documentation for ongoing VideoCore firmware tooling. Sparse churn argues for annotation, but current hardware sales and lack of a natural replacement argue against deprecation/removal.