195c7d59bc
There is new patch-status QA check in oe-core: https://git.openembedded.org/openembedded-core/commit/?id=76a685bfcf927593eac67157762a53259089ea8a This is temporary work around just to hide _many_ warnings from optional patch-status (if you add it to WARN_QA). This just added Upstream-Status: Pending everywhere without actually investigating what's the proper status. This is just to hide current QA warnings and to catch new .patch files being added without Upstream-Status, but the number of Pending patches is now terrible: Patches in Pending state: 41 (57%) With recent change to enable patch-status not only for all .patch files in oe-core, but for all recipes from oe-core: https://git.openembedded.org/openembedded-core/commit/?id=61a881fdbe8b5a21c6276b8a5d06cc30486b1eb3 this causes bluez5 do_patch failures as reported in: https://lists.openembedded.org/g/openembedded-core/message/183177 Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
meta-raspberrypi
Yocto BSP layer for the Raspberry Pi boards - http://www.raspberrypi.org/.
|
Sponsored by:
|
Quick links
- Git repository web frontend: https://github.com/agherzan/meta-raspberrypi
- Mailing list (yocto mailing list): yocto@lists.yoctoproject.org
- Issues management (Github Issues): https://github.com/agherzan/meta-raspberrypi/issues
- Documentation: http://meta-raspberrypi.readthedocs.io/en/latest/
Description
This is the general hardware specific BSP overlay for the RaspberryPi device.
More information can be found at: http://www.raspberrypi.org/ (Official Site)
The core BSP part of meta-raspberrypi should work with different OpenEmbedded/Yocto distributions and layer stacks, such as:
- Distro-less (only with OE-Core).
- Yoe Disto (Video and Camera Products).
- Yocto/Poky (main focus of testing).
Yocto Project Compatible Layer
This layer is officially approved as part of the Yocto Project Compatible Layers Program. You can find details of that on the official Yocto Project
website.
Dependencies
This layer depends on:
- URI: git://git.yoctoproject.org/poky
- branch: master
- revision: HEAD
Quick Start
- source poky/oe-init-build-env rpi-build
- Add this layer to bblayers.conf and the dependencies above
- Set MACHINE in local.conf to one of the supported boards
- bitbake core-image-base
- Use bmaptool to copy the generated .wic.bz2 file to the SD card
- Boot your RPI
Quick Start with kas
- Install kas build tool from PyPi (sudo pip3 install kas)
- kas build meta-raspberrypi/kas-poky-rpi.yml
- Use bmaptool to copy the generated .wic.bz2 file to the SD card
- Boot your RPI
To adjust the build configuration with specific options (I2C, SPI, ...), simply add a section as follows:
local_conf_header:
rpi-specific: |
ENABLE_I2C = "1"
RPI_EXTRA_CONFIG = "dtoverlay=pi3-disable-bt"
To configure the machine, you have to update the machine variable.
And the same for the distro.
For further information, you can read more at https://kas.readthedocs.io/en/latest/index.html
Contributing
You can send patches using the GitHub pull request process or/and through the Yocto mailing list. Refer to the documentation for more information.
Maintainers
- Andrei Gherzan
<andrei at gherzan.com>