Re: [meta-ti][master/wrynose][PATCH] linux-firmware: Move recipe from meta-arago

On 6/25/26 11:14 AM, Ryan Eatmon wrote:
>=20
> Is there a good reason that you dropped the guard structure that meta-a=
rago had when you ported it over to meta-ti?=C2=A0 Even though what you a=
re doing is technically ok, it still stands out versus almost all other b=
bappend patterns that we have in both repos.
>=20

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

>=20
> 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]>
>> ---
>> =C2=A0 .../linux-firmware/linux-firmware_%.bbappend=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 | 7 +++++=
++
>> =C2=A0 1 file changed, 7 insertions(+)
>> =C2=A0 create mode 100644 meta-ti-bsp/recipes-kernel/linux-firmware/li=
nux-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_%.b=
bappend
>> new file mode 100644
>> index 00000000..b37bec7a
>> --- /dev/null
>> +++ b/meta-ti-bsp/recipes-kernel/linux-firmware/linux-firmware_%.bbapp=
end
>> @@ -0,0 +1,7 @@
>> +PR:append:ti-soc =3D ".tisoc1"
>> +
>> +# meta-ti-bsp packages newer versions on these
>> +do_install:append:ti-soc() {
>> +=C2=A0=C2=A0=C2=A0 rm -rf ${D}${nonarch_base_libdir}/firmware/ti-conn=
ectivity/
>> +=C2=A0=C2=A0=C2=A0 rm -rf ${D}${nonarch_base_libdir}/firmware/cadence=
/
>> +}
>=20