From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH-NEXT 4/4] linux: build after linux-firmware if enabled for early loading support
Date: Sat, 13 Feb 2021 11:32:16 +0100 [thread overview]
Message-ID: <87sg60cl73.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210213101326.GR1679218@scaer> (Yann E. MORIN's message of "Sat, 13 Feb 2021 11:13:26 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> On 2021-02-12 19:40 +0100, Peter Korsgaard spake thusly:
>> To support building in (a subset of) the linux-firmware files into the
>> kernel using the CONFIG_EXTRA_FIRMWARE option, we need to ensure that the
>> firmware files are installed before the Linux kernel is built, similar to
>> how it is done for intel-microcode.
>>
>> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
>> ---
>> linux/linux.mk | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/linux/linux.mk b/linux/linux.mk
>> index a212f42c28..5e4b319cf1 100644
>> --- a/linux/linux.mk
>> +++ b/linux/linux.mk
>> @@ -78,7 +78,8 @@ LINUX_MAKE_ENV = \
>>
>> LINUX_INSTALL_IMAGES = YES
>> LINUX_DEPENDENCIES = host-kmod \
>> - $(if $(BR2_PACKAGE_INTEL_MICROCODE),intel-microcode)
>> + $(if $(BR2_PACKAGE_INTEL_MICROCODE),intel-microcode) \
>> + $(if $(BR2_PACKAGE_LINUX_FIRMWARE),linux-firmware)
> You also need to tell the kernel where to find those firmware files,
> with CONFIG_EXTRA_FIRMWARE_DIR, otherwise it will look in /lib/firmware.
Yes, but that you can take care of in linux config file/fragment. We
already expose BR2_BINARIES_DIR in the environment for this, E.G. you
can do:
CONFIG_EXTRA_FIRMWARE_DIR="${BR_BINARIES_DIR}"
CONFIG_EXTRA_FIRMWARE="intel-ucode/06-5e-03 i915/kbl_dmc_ver1_04.bin"
(or whatever files you want to include).
> So we'd need something like:
> $(if $(BR2_PACKAGE_LINUX_FIRMWARE),
> $(call KCONFIG_SET_OPT,CONFIG_EXTRA_FIRMWARE_DIR,"$${BR_BINARIES_DIR}/linux-firmware"))
NIT: Only ${BR_BINARIES_DIR}, not a linux-firmware subdir, otherwise you
cannot include both microcode and linux-firmware files.
> (note the $$ escaping and the use of a shell-level variable, like is
> done for CONFIG_INITRAMFS_SOURCE).
Given that the user already has to use a custom kernel config
file/fragment to specify what files to include, I don't think it makes
sense to override the CONFIG_EXTRA_FIRMWARE_DIR setting. We don't do it
for intel-microcode either.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-02-13 10:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 18:40 [Buildroot] [PATCH-NEXT 0/4] package/linux-firmware: install into images for early loading support Peter Korsgaard
2021-02-12 18:40 ` [Buildroot] [PATCH-NEXT 1/4] package/linux-firmware: make target install macros accept a destination parameter Peter Korsgaard
2021-02-12 18:40 ` [Buildroot] [PATCH-NEXT 2/4] package/linux-firmware.mk: get rid of temporary tarball for file installation Peter Korsgaard
2021-02-12 20:39 ` Yann E. MORIN
2021-02-12 21:07 ` Yann E. MORIN
2021-02-13 8:35 ` Yann E. MORIN
2021-02-13 9:46 ` Peter Korsgaard
2021-02-13 10:05 ` Yann E. MORIN
2021-02-12 21:37 ` Peter Korsgaard
2021-02-13 8:37 ` Yann E. MORIN
2021-02-13 9:47 ` Peter Korsgaard
2021-02-13 9:51 ` Yann E. MORIN
2021-02-13 10:14 ` Peter Korsgaard
2021-02-13 10:19 ` Yann E. MORIN
2021-02-13 10:26 ` Peter Korsgaard
2021-02-12 18:40 ` [Buildroot] [PATCH-NEXT 3/4] package/linux-firmware: also install into images for early loading support Peter Korsgaard
2021-02-12 18:40 ` [Buildroot] [PATCH-NEXT 4/4] linux: build after linux-firmware if enabled " Peter Korsgaard
2021-02-13 10:13 ` Yann E. MORIN
2021-02-13 10:32 ` Peter Korsgaard [this message]
2021-02-13 13:26 ` Yann E. MORIN
2021-02-13 15:24 ` Peter Korsgaard
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=87sg60cl73.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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