From: Ryan Eatmon <reatmon@ti.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH v2] linux-firmware: Move all firmware into sub-packages
Date: Thu, 9 Oct 2025 10:00:45 -0500 [thread overview]
Message-ID: <913e6202-9c78-446e-bbec-59bd17b454ae@ti.com> (raw)
In-Reply-To: <D8E485CB-74EA-4719-BAAE-2E4CE23CC7EB@arm.com>
On 10/9/2025 9:23 AM, Ross Burton wrote:
> On 7 Oct 2025, at 16:46, Ryan Eatmon via lists.openembedded.org <reatmon=ti.com@lists.openembedded.org> wrote:
>>
>> A lot of the firmware has already been broken out into sub-packages, but
>> a good number were still lingering in the base linux-firmware package.
>>
>> This patch does two things:
>>
>> 1) Move all of the remaining firmware into sub-packages based on the
>> driver name in the WHENCE file or into existing sub-packages where a
>> file or two were missed.
>>
>> 2) Create a new REMOVE_UNLICENSED variable and do_install() logic to
>> allow for marking certain firmware files as something to remove and not
>> package up. The intention is that in the WHENCE file, a number of
>> firmware files have no license information or very questionable
>> declarations as to what the license is for the firmware.
>
> I’m tempted to ask for (1) and (2) to be split into separate patches, but importantly this empties PN but doesn’t set ALLOW_EMPTY, so the meta-package to let you install all the firmware no longer exists.
>
> Can you set ALLOW_EMPTY:${PN} = “1” so that linux-firmware is still built (albeit empty).
Sure. I'll split this into three patches.
1) Bin everything (with a license).
2) Add the remove logic for the remaining unlicensed code, and set
ALLOW_EMPTY.
3) Set FILES:${PN}="" with comment to make it clear what the new policy is.
Just to make it super clear what each patch is doing.
> Ross
--
Ryan Eatmon reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc. - LCPD - MGTS
prev parent reply other threads:[~2025-10-09 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 15:46 [OE-core][PATCH v2] linux-firmware: Move all firmware into sub-packages Ryan Eatmon
2025-10-07 16:00 ` Alexander Kanavin
2025-10-07 16:15 ` Ryan Eatmon
2025-10-09 14:23 ` Ross Burton
2025-10-09 15:00 ` Ryan Eatmon [this message]
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=913e6202-9c78-446e-bbec-59bd17b454ae@ti.com \
--to=reatmon@ti.com \
--cc=Ross.Burton@arm.com \
--cc=openembedded-core@lists.openembedded.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