From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] [git commit branch/2021.11.x] linux: build after wireless-regdb if enabled for early loading support
Date: Sun, 27 Feb 2022 20:16:39 +0100 [thread overview]
Message-ID: <20220227192002.6D9888212C@busybox.osuosl.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1376 bytes --]
commit: https://git.buildroot.net/buildroot/commit/?id=e91440b904a6bae850a503f0938f833a5691d951
branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/2021.11.x
To support building in the wireless regulatory database files (regulatory.db*)
into the kernel using the CONFIG_EXTRA_FIRMWARE option, we need to ensure that
the database files are installed before the Linux kernel is built.
The dependency is harmless if CONFIG_EXTRA_FIRMWARE isn't actually set.
Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
(cherry picked from commit de0f5ba17a15a87bc16a6d6aa318104510c38f9d)
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 b047061c3d..960a4ebd63 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -72,7 +72,8 @@ LINUX_MAKE_ENV = \
LINUX_INSTALL_IMAGES = YES
LINUX_DEPENDENCIES = host-kmod \
$(if $(BR2_PACKAGE_INTEL_MICROCODE),intel-microcode) \
- $(if $(BR2_PACKAGE_LINUX_FIRMWARE),linux-firmware)
+ $(if $(BR2_PACKAGE_LINUX_FIRMWARE),linux-firmware) \
+ $(if $(BR2_PACKAGE_WIRELESS_REGDB),wireless-regdb)
# Starting with 4.16, the generated kconfig paser code is no longer
# shipped with the kernel sources, so we need flex and bison, but
[-- Attachment #2: Type: text/plain, Size: 150 bytes --]
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-02-27 19:28 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=20220227192002.6D9888212C@busybox.osuosl.org \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.