// the find
agherzan/meta-raspberrypi
Yocto/OE BSP layer for the Raspberry Pi boards
A Yocto/OpenEmbedded BSP layer that adds Raspberry Pi board support (boot firmware, kernel, graphics stack, Bluetooth, GPIO) to a custom embedded Linux build. It's for people building their own RPi image with bitbake, not for anyone just flashing Raspberry Pi OS.
Machine configs cover the full board lineup from the original Pi Zero through the Pi 5 and CM variants, and kernel recipes track three live branches (6.1, 6.6, 6.12, 6.18) so you can pick an LTS line instead of being stuck on one kernel. It's an officially approved Yocto Project Compatible layer, which means it actually passes yocto-check-layer rather than just claiming compatibility. kas config files are included, so you can reproduce a build without hand-assembling bblayers.conf and local.conf. CI builds Docker images and runs layer compliance checks on every push.
The patch count on things like userland and rpidistro-vlc (two dozen-plus patches each) shows how much forward-porting this layer has to carry just to keep Broadcom's proprietary graphics stack building against current kernels — that's ongoing maintenance debt that lands on you too if you fork a kernel version. The README gives a quick-start but says nothing about which combination of meta-openembedded dynamic layers you actually need for a working image (Python, Qt5, multimedia are all separate bbappends scattered across dynamic-layers/), so first-time integration is trial and error. No real architecture doc on when to use rpi-config vs. firmware recipes vs. the kernel .cfg fragments — you're expected to already know Yocto's layering conventions. Single named maintainer for a layer this depended-upon is a bus-factor risk.