From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH-NEXT v2 0/4] package/linux-firmware: install into images for early loading support
Date: Mon, 15 Feb 2021 17:05:53 +0100 [thread overview]
Message-ID: <20210215160558.19574-1-peter@korsgaard.com> (raw)
Some drivers request their firmware very early when built into the
kernel, even before the initramfs is mounted - So the only way to
provide firmware for those drivers is to include them directly in the
kernel with the CONFIG_EXTRA_FIRMWARE option.
To support this, let linux-firmware install its files into
BINARIES_DIR in addition to TARGET_DIR, similar to how we do it for
intel-microcode.
Peter Korsgaard (3):
package/linux-firmware: make install logic macro accept a destination
parameter
package/linux-firmware: also install into images for early loading
support
linux: build after linux-firmware if enabled for early loading support
Yann E. MORIN (1):
package/linux-firmware: rationalise install step
linux/linux.mk | 3 ++-
package/linux-firmware/linux-firmware.mk | 34 +++++++++---------------
2 files changed, 15 insertions(+), 22 deletions(-)
--
2.20.1
next reply other threads:[~2021-02-15 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 16:05 Peter Korsgaard [this message]
2021-02-15 16:05 ` [Buildroot] [PATCH-NEXT v2 1/4] package/linux-firmware: rationalise install step Peter Korsgaard
2021-02-15 16:05 ` [Buildroot] [PATCH-NEXT v2 2/4] package/linux-firmware: make install logic macro accept a destination parameter Peter Korsgaard
2021-02-15 16:05 ` [Buildroot] [PATCH-NEXT v2 3/4] package/linux-firmware: also install into images for early loading support Peter Korsgaard
2021-02-15 16:05 ` [Buildroot] [PATCH-NEXT v2 4/4] linux: build after linux-firmware if enabled " Peter Korsgaard
2021-02-23 12:50 ` [Buildroot] [PATCH-NEXT v2 0/4] package/linux-firmware: install into images " 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=20210215160558.19574-1-peter@korsgaard.com \
--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 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.