On Fri, Sep 11, 2026 at 05:13:15PM -0500, Ryan Eatmon via
lists.yoctoproject.org wrote:
>
>
> On 9/11/2026 1:39 PM, Thorsten Lannynd wrote:
> >Split force-h264-youtube into its own package, enabled only on boards that
> >support
> >H264 YouTube hardware accelerated playback.
> >
> >Signed-off-by: Thorsten Lannynd <[email protected]>
> >---
> >
> >v2:
> >- Shorten commit message title
> >
> > .../chromium/chromium-ozone-wayland-arago.inc | 29 ++++++++++++++-----
> > 1 file changed, 22 insertions(+), 7 deletions(-)
> >
> >diff --git
> >a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >
> >b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >index d8eb0204..108f77c7 100644
> >---
> >a/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >+++
> >b/meta-arago-distro/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland-arago.inc
> >@@ -1,6 +1,6 @@
> > PR:append = ".arago0"
> >-EXTENSION_DIR = "/usr/lib/chromium/extensions/force-h264-youtube"
> >+EXTENSION_DIR = "${libdir}/chromium/extensions/force-h264-youtube"
> > FILESEXTRAPATHS:prepend := "${THISDIR}/chromium-ozone-wayland:"
> >@@ -15,11 +15,26 @@ SRC_URI:append = " \
> > file://force-h264-youtube/manifest.json \
> > "
> >+PACKAGES:append = " ${PN}-force-h264-youtube"
> >+FILES:${PN}-force-h264-youtube = "${EXTENSION_DIR}"
> >+RDEPENDS:${PN}-force-h264-youtube = "${PN}"
> >+
> >+CHROMIUM_H264_EXT ?= ""
> >+CHROMIUM_H264_EXT:am62pxx-evm = "1"
> >+CHROMIUM_H264_EXT:j721s2-evm = "1"
> >+CHROMIUM_H264_EXT:j722s-evm = "1"
> >+CHROMIUM_H264_EXT:j742s2-evm = "1"
> >+CHROMIUM_H264_EXT:j784s4-evm = "1"
>
> Would it be better to create a MACHINE_FEATURES for h264 and then
> have this just key off that. Then you could send a second patch to
> meta-ti-bsp that adds that feature?
>
> Denys, thoughts?
Yeah, MACHINE_FEATURES makes sense.
Looking over the corresponding data sheets, both H.264 and H.265 are handled
by the Wave5 Codec IP in SoC. And for those SoCs we have "cnm-wave-fw" FW
recipe in meta-ti that gets pulled by MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS
list. So, another option would be to check if "cnm-wave-fw" exists in this
list...
But, making this conditional on machine or its features inside chromium recipe
will have ill effects - the resulting package will no longer can be re-used
across machines of the same architecture. The entire chromium package will
have to be marked as machine-specific and gets rebuilt for each machine, due
to the next line below:
> >+RRECOMMENDS:${PN}:append = " ${@bb.utils.contains('CHROMIUM_H264_EXT', '1',
> >'${PN}-force-h264-youtube', '', d)}"
> >+
> > do_install:append() {
> >- install -d ${D}${EXTENSION_DIR}
> >- install -m 0644 ${WORKDIR}/sources/force-h264-youtube/force_h264.js \
> >- ${WORKDIR}/sources/force-h264-youtube/manifest.json \
> >- ${D}${EXTENSION_DIR}/
> >+ if [ -n "${CHROMIUM_H264_EXT}" ]; then
> >+ install -d ${D}${EXTENSION_DIR}
> >+ install -m 0644 ${WORKDIR}/sources/force-h264-youtube/force_h264.js
> >\
> >+ ${WORKDIR}/sources/force-h264-youtube/manifest.json
> >\
> >+ ${D}${EXTENSION_DIR}/
> >+ sed -i "s|CHROME_EXTRA_ARGS=\"\(.*\)\"|CHROME_EXTRA_ARGS=\"\1
> >--load-extension=${EXTENSION_DIR}\"|" \
> >+ ${D}${libdir}/chromium/chromium-wrapper
> >+ fi
> > }
> >-
> >-FILES:${PN}:append = " ${EXTENSION_DIR}"
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#17671):
https://lists.yoctoproject.org/g/meta-arago/message/17671
Mute This Topic: https://lists.yoctoproject.org/mt/121203666/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-arago/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
