Go to file
Vincent Davis Jr 1f33240549 rpidistro-ffmpeg: upgrade 4.3.2 -> 4.3.4
Upgrades version of ffmpeg to 4.3.4
* Reason for not upgrading to 4.3.5 all ported raspberrypi
  team patches may not be included in that version/commit.
* SRCREV set to 246e1a55a0eca931537d8706acd8b133c07beb05

Updates to PACKAGECONFIG
* Only include --enable-opengl flag when opengl is set in
  DISTRO_FEATURES
* Add new flag --enable-epoxy required by vout-egl
* vout-egl requires both libepoxy and x11. Only
  enable vout-egl if x11 contained in DISTRO_FEATURES.
* The remaining RPI-Distro related flags added
  through patches. Are only enabled if vc4graphics
  is disabled and userland graphics enabled. As an
  attempt to keep ffmpeg ./configure generic unless
  specified other wise.

Removes TARGET_CFLAGS:append as include flags are set in
./configure via the 2001-configure-setup-for-OE-core-usage.patch
patch.

Replaces patches with updated patches used in actual commit.
Adds four new patches to fix ./configure, compile, runtime bugs.

PATCHES:
- 2001-configure-setup-for-OE-core-usage.patch
* The ./configure stage fails if neither x11 or wayland defined
  in DISTRO_FEATURES. When opengl enabled ./configure checks for
  relevant headers. The last header it checks for is ES2/gl.h which
  doesn't exists. Neither do the others if certain perameters
  are not meet. Patch addes check for GLES2/gl2.h which does
  exists. We use utilize GLESv2 to compile and link with.
  Patch also replaces where compiler find mmal and omx headers
  and libs.

- 2002-libavdevice-opengl_enc-update-dynamic-function-loader.patch
* After configure stage succeeds the compile stage fails as
  SelectedGetProcAddress isn't defined. It can't be define as
  if x11 isn't enabled. Patch defines SelectedGetProcAddress
  if x11 not enabled, but sdl2 enabled to SDL_GL_GetProcAddress.
  If neither sdl2 or x11 is enabled patch loads GL functions
  pointers at compile time versus dynamically at runtime.

- 2003-libavcodec-fix-v4l2_req_devscan.patch
* v412_req_devscan.h function definitions where different
  from v412_req_devscan.c function implementations.

- 2004-libavcodec-omx-replace-opt-vc-path-with-usr-lib.patch
* Fixes where libbcm_host.so and libopenmaxil.so are loaded from.

Signed-off-by: Vincent Davis Jr <vince@underview.tech>
2022-12-13 02:32:11 +00: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 rpi-default-providers: add libav and libpostproc 2022-12-13 01:00:53 +00:00
docs Add support for a ARMv8 machine supporting multiple Raspberry Pi boards 2022-09-14 20:39:18 +01:00
dynamic-layers rpidistro-vlc: upgrade 3.0.12 -> 3.0.17 2022-12-12 23:29:00 +00: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 rpi-cmdline: Leave cma value to kernel default 2022-10-11 00:24:39 +01:00
recipes-connectivity recipes: Update SRC_URI protocols for github 2021-11-07 21:30:23 +00:00
recipes-core packagegroup-rpi-test: Include more packages 2022-04-21 21:41:38 +01:00
recipes-devtools python3-adafruit-circuitpython-register: Bump to 1.9.10 2022-07-31 02:16:37 +01:00
recipes-graphics userland: Bump revision to the current HEAD 2022-07-31 02:16:37 +01:00
recipes-kernel Add support for a ARMv8 machine supporting multiple Raspberry Pi boards 2022-09-14 20:39:18 +01:00
recipes-multimedia rpidistro-ffmpeg: upgrade 4.3.2 -> 4.3.4 2022-12-13 02:32:11 +00: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>