* linux-firmware embedded usecase, licenses.
@ 2022-01-26 13:07 Christian Melki
0 siblings, 0 replies; only message in thread
From: Christian Melki @ 2022-01-26 13:07 UTC (permalink / raw)
To: linux-firmware; +Cc: linux-kernel
Hi.
I have this usecase where I include selected parts of linux-firmware on
an embedded machine. As the entire archive is pretty large, only the
needed bits are copied.
Now my issue is that typical embedded build environments create their
own little version of license/information selection hell. They do it so
they can figure out which files belong to what license, etc.
https://github.com/buildroot/buildroot/blob/master/package/linux-firmware/linux-firmware.mk
https://git.yoctoproject.org/poky/plain/meta/recipes-kernel/linux-firmware/linux-firmware_20211216.bb
(and others)
So instead of everyone trying to work out the same information (and
checking the integrity of that on every release), it would be nice if
the WHENCE file was a bit more structured. That would help something
like copy-firmware.sh (or similar) to do most of the mundane bits.
Regards,
Christian
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-01-26 13:08 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-26 13:07 linux-firmware embedded usecase, licenses Christian Melki
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).