On 6/25/26 11:14 AM, Ryan Eatmon wrote:
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
On 6/25/2026 10:58 AM, Andrew Davis wrote:
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
diff --git
a/meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
b/meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
new file mode 100644
index 00000000..b37bec7a
--- /dev/null
+++ b/meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbappend
@@ -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/
+}
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#20095):
https://lists.yoctoproject.org/g/meta-ti/message/20095
Mute This Topic: https://lists.yoctoproject.org/mt/119975851/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
