linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: linux-firmware@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: linux-firmware embedded usecase, licenses.
Date: Wed, 26 Jan 2022 14:07:16 +0100	[thread overview]
Message-ID: <17d7548a-9f6b-dacc-2f96-9d625fc080a5@t2data.com> (raw)

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

                 reply	other threads:[~2022-01-26 13:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=17d7548a-9f6b-dacc-2f96-9d625fc080a5@t2data.com \
    --to=christian.melki@t2data.com \
    --cc=linux-firmware@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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).