linux-firmware: Move recipe from meta-arago
PATCH 1/1 linux-firmware: Move recipe from meta-arago
The conflicting firmware packages that necessitate this bbappend are all here in meta-ti-bsp, so this will be needed by any distro using this layer. Move this bbappend out of meta-arago to this layer.
--- .../linux-firmware/linux-firmware_%.bbappend | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend new file +7 -0
@@ -0,0 +1,7 @@ +PR:append:ti-soc = ".tisoc1" + +# meta-ti-bsp packages newer versions on these +do_install:append:ti-soc() { + rm -rf ${D}${nonarch_base_libdir}/firmware/ti-connectivity/ + rm -rf ${D}${nonarch_base_libdir}/firmware/cadence/ +}
Signature · 1 line
2.39.2
meta-ti / na / 20260625155800.28627-1-afd
PRC Results: FAIL
=========================================================
check-yocto-patches: PASS
=========================================================
Patches
----------------------------------------
All patches passed
=========================================================
apply-yocto-patch: PASS
=========================================================
master
=====================
Summary:
- Patch Series: [meta-ti][master/wrynose][PATCH] linux-firmware: Move recipe from meta-arago
- Submitter: From: Andrew Davis <[email protected]>
- Date: Date: Thu, 25 Jun 2026 10:58:00 -0500
- Num Patches: 1
- Mailing List (public inbox) Commit SHA: 0299ddb1d9ece21f81362bbd840e9b679500493a
Applied to:
- Repository: lcpd-prc-meta-ti
- Base Branch: master-wip
- Commit Author: Ryan Eatmon <[email protected]>
- Commit Subject: TEST: linux-ti-staging: Add testing dtbo and build command
- Commit SHA: 07bd4c181e2a400d4375ddad7a20fbba6578b133
Patches
----------------------------------------
All patches applied
wrynose
=====================
Summary:
- Patch Series: [meta-ti][master/wrynose][PATCH] linux-firmware: Move recipe from meta-arago
- Submitter: From: Andrew Davis <[email protected]>
- Date: Date: Thu, 25 Jun 2026 10:58:00 -0500
- Num Patches: 1
- Mailing List (public inbox) Commit SHA: 0299ddb1d9ece21f81362bbd840e9b679500493a
Applied to:
- Repository: lcpd-prc-meta-ti
- Base Branch: wrynose-wip
- Commit Author: Suhaas Joshi <[email protected]>
- Commit Subject: tfa: Update TF-A for K3 devices to 2.15 tag
- Commit SHA: 88ce8160ec6c5804820555e0bc29dba23059a4a1
Patches
----------------------------------------
All patches applied
=========================================================
check-yocto-repo: FAIL
=========================================================
master
=====================
FAIL
WARN: .bbappend files might need a guard to make them check-layer compliant. (GUARD-1)
meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887
wrynose
=====================
FAIL
WARN: .bbappend files might need a guard to make them check-layer compliant. (GUARD-1)
meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
For details on the above errors/warnings visit: https://lists.yoctoproject.org/g/meta-ti/wiki/40887
Is there a good reason that you dropped the guard structure that meta-arago had when you ported it over to meta-ti? Even though what you are doing is technically ok, it still stands out versus almost all other bbappend patterns that we have in both repos.
Quoted 23 lines · Andrew Davis
The conflicting firmware packages that necessitate this bbappend are all here in meta-ti-bsp, so this will be needed by any distro using this layer. Move this bbappend out of meta-arago to this layer.
Signed-off-by Andrew Davis <[email protected]>--- .../linux-firmware/linux-firmware_%.bbappend | 7 +++++++ 1 file changed, 7 insertions(+)create mode 100644 meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend new file +7
-0@@ -0,0 +1,7 @@ +PR:append:ti-soc = ".tisoc1" + +# meta-ti-bsp packages newer versions on these +do_install:append:ti-soc() { + rm -rf ${D}${nonarch_base_libdir}/firmware/ti-connectivity/ + rm -rf ${D}${nonarch_base_libdir}/firmware/cadence/ +}
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Quoted 3 lines · Ryan Eatmon
Is there a good reason that you dropped the guard structure that meta-arago had when you ported it over to meta-ti? Even though what you are doing is technically ok, it still stands out versus almost all other bbappend patterns that we have in both repos.
It just felt unnecessary to do that two file indirection thing that some other bbappends do on such a simple update, perhaps some other bbappends should look more like this one instead..
And this isn't the only bbappend like this in meta-ti, see
- binutils-cross-canadian_%.bbappend
- eudev_%.bbappend
Andrew
Quoted 26 lines · Andrew Davis
Quoted 23 lines
The conflicting firmware packages that necessitate this bbappend are all here in meta-ti-bsp, so this will be needed by any distro using this layer. Move this bbappend out of meta-arago to this layer.
Signed-off-by Andrew Davis <[email protected]>---
.../linux-firmware/linux-firmware_%.bbappend | 7 +++++++1 file changed, 7 insertions(+)create mode 100644 meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend new file +7
-0@@ -0,0 +1,7 @@ +PR:append:ti-soc = ".tisoc1" + +# meta-ti-bsp packages newer versions on these +do_install:append:ti-soc() { + rm -rf ${D}${nonarch_base_libdir}/firmware/ti-connectivity/ + rm -rf ${D}${nonarch_base_libdir}/firmware/cadence/ +}