I think it would be more in keeping with the Yocto way if all these
firmware capabilities were added through PACKAGECONFIG options in a
meta-ti bbappend to linux-firmware, rather than through separate recipes.
This is especially true of the firmware added in linux-staging-ti. If
those patches are ever upstreamed (I assume that's the intent) then
stock linux-yocto kernels will be getting the images from
linux-firmware, and updated versions obtained in future linux-staging-ti
branches will conflict.
Last I looked, linux-staging-ti had a .elf format firmware blob, which
is not a supported format for linux-firmware. Adding it in a bbappend
produces a QA warning because it gets stripped and the debug version
doesn't get packaged. At that time, although both .bin and .elf
versions of that firmware were available, the code that loaded it would
only work with the .elf version.
In short, consistently putting firmware into linux-firmware now would
decrease integration issues both now and in the future.
Just a thought.
Peter
--
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti
