All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorsten Lannynd <t-lannynd@ti.com>
To: <meta-arago@lists.yoctoproject.org>, <reatmon@ti.com>
Cc: <detheridge@ti.com>, <b-brnich@ti.com>
Subject: [meta-arago][master/wrynose][PATCH] meta-arago-disto: chromium: restrict force-h264-youtube extension to supported boards
Date: Fri, 11 Sep 2026 13:24:32 -0500	[thread overview]
Message-ID: <20260911182432.526086-1-t-lannynd@ti.com> (raw)

Split force-h264-youtube into its own package, enabled only on boards that
support H264 YouTube hardware accelerated playback.

Signed-off-by: Thorsten Lannynd <t-lannynd@ti.com>
---
 .../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"
+
+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}"
-- 
2.34.1



             reply	other threads:[~2026-09-11 18:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-11 18:24 Thorsten Lannynd [this message]
2026-09-11 18:35 ` [meta-arago][master/wrynose][PATCH] meta-arago-disto: chromium: restrict force-h264-youtube extension to supported boards PRC Automation

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260911182432.526086-1-t-lannynd@ti.com \
    --to=t-lannynd@ti.com \
    --cc=b-brnich@ti.com \
    --cc=detheridge@ti.com \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.