Go to file
Martin Jansa 195c7d59bc *.patch: add Upstream-Status to all patches
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>
2023-06-22 00:04:40 +01:00
.github ci: Fix dco-check job with newer git versions 2022-11-08 08:21:47 +00:00
classes sdcard_image-rpi.bbclass: Move SDIMG_KERNELIMAGE definitions to their machines 2022-09-14 20:39:18 +01:00
conf machines: simplify MACHINEOVERRIDES definitions 2023-05-24 11:30:04 +01:00
docs rpi-config: U-Boot requires "enable_uart=1" to operate correctly. 2023-06-09 02:09:42 +01:00
dynamic-layers python3-adafruit-blinka: Fix the correct python recipes path in dynamic-layer sub-dir 2023-04-17 11:06:52 +01:00
files/custom-licenses bcm2835-bootfiles: Clarify license conditions 2019-10-24 14:08:16 +01:00
img Use a png with transparency for balena logo 2022-07-31 02:18:20 +01:00
lib/oeqa/runtime/cases parselogs: Update the error regexps to 5.10 kernel 2021-11-23 11:32:35 +00:00
recipes-bsp *.patch: add Upstream-Status to all patches 2023-06-22 00:04:40 +01:00
recipes-connectivity *.patch: add Upstream-Status to all patches 2023-06-22 00:04:40 +01:00
recipes-core udev-rules-rpi: Use 99-com.rules directly from upstream 2023-05-28 10:19:52 +01:00
recipes-devtools python3-adafruit-circuitpython-register: Bump to 1.9.10 2022-07-31 02:16:37 +01:00
recipes-graphics *.patch: add Upstream-Status to all patches 2023-06-22 00:04:40 +01:00
recipes-kernel *.patch: add Upstream-Status to all patches 2023-06-22 00:04:40 +01:00
recipes-multimedia *.patch: add Upstream-Status to all patches 2023-06-22 00:04:40 +01:00
recipes-sato libwpe: Migrate build workaround from oe-core 2021-11-14 15:39:24 +00:00
wic sdimage-raspberrypi.wks: find /boot partition on mmcblk0 2018-03-07 23:35:18 +00:00
.gitignore gitignore: Ignore .pyc files 2021-03-24 10:07:46 +00:00
.readthedocs.yaml docs: Add module dependency/requirement for RtD 2021-11-14 01:03:59 +00:00
COPYING.MIT COPYING.MIT: Add license file for the metadata. 2012-04-03 20:44:03 +01:00
kas-poky-rpi.yml kas: local.conf: disable prelink 2021-08-09 15:23:22 +03:00
README.md README.md: Refactor top table 2022-07-31 02:18:20 +01:00

meta-raspberrypi

Yocto BSP layer for the Raspberry Pi boards - http://www.raspberrypi.org/.

Documentation Status Matrix


Yocto Project Layer Compatible
Sponsored by:
balena.io

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

  1. source poky/oe-init-build-env rpi-build
  2. Add this layer to bblayers.conf and the dependencies above
  3. Set MACHINE in local.conf to one of the supported boards
  4. bitbake core-image-base
  5. Use bmaptool to copy the generated .wic.bz2 file to the SD card
  6. Boot your RPI

Quick Start with kas

  1. Install kas build tool from PyPi (sudo pip3 install kas)
  2. kas build meta-raspberrypi/kas-poky-rpi.yml
  3. Use bmaptool to copy the generated .wic.bz2 file to the SD card
  4. 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>