summaryrefslogtreecommitdiffstats
path: root/meta-agl-bsp/meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bbappend
diff options
context:
space:
mode:
authorScott Murray <scott.murray@konsulko.com>2024-04-18 16:46:07 -0400
committerJan-Simon Möller <jsmoeller@linuxfoundation.org>2024-04-26 16:15:24 +0200
commit69ff63db4d9d162247c974641a53787ba9ed6931 (patch)
treea8a9057fe2832c9c8e19efdd27bde813f059feaa /meta-agl-bsp/meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bbappend
parent430b34fb2e9c9e03f91996935ad84d1319ed6733 (diff)
Work around rcar-gen3 gstreamer issues
The scarthgap-dev branch of meta-rcar-gen3 has bbappends for the gstreamer1.0-plugins-* and gstreamer1.0-omx recipes that effectively build the Renesas 1.20.3 forks and package them as 1.22.x. This breaks building gstreamer users since there are mismatches between the main gstreamer package contents and the plugins. To fix this for now: - BBMASK out the bbappends - Update our gstreamer1.0-plugins-bad bbappend to enable the KMS plugin to avoid breaking the BSP gstreamer plugins packagegroup. This can be removed once we no longer need to BBMASK the upstream bbappends. - Remove the rcar-gen3 version of our local patch against gstreamer1.0-plugins-bad, as it no longer applies (since rcar-gen3 will be using the upstream version for now). This can be revisited when meta-rcar-gen3 is updated to resolve the mismatch. As a bonus, the now unnecessary network flag overrides we were doing for the gstreamer plugin recipes have been removed, as they are no longer required. Bug-AGL: SPEC-4578 Change-Id: I4e6f1646c93d981744e65dddf6753c3dc005426e Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Diffstat (limited to 'meta-agl-bsp/meta-raspberrypi/recipes-bsp/bootfiles/rpi-config_git.bbappend')
0 files changed, 0 insertions, 0 deletions