From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] linux: install firmware to staging.
Date: Mon, 8 Jul 2013 19:52:21 +0200 [thread overview]
Message-ID: <20130708175221.GE3206@free.fr> (raw)
In-Reply-To: <1373239866-18076-1-git-send-email-spenser@gillilanding.com>
On 2013-07-07 18:31 -0500, Spenser Gilliland spake thusly:
> Install firmware to staging when the hidden option
> BR2_LINUX_KERNEL_INSTALL_FIRMWARE is selected. This allows parts of the
> firmware provided by the linux kernel to be installed in the target.
>
> Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
> ---
> linux/Config.in | 5 +++++
> linux/linux.mk | 13 +++++++++++++
> 2 files changed, 18 insertions(+)
>
> diff --git a/linux/Config.in b/linux/Config.in
> index f58e714..b733019 100644
> --- a/linux/Config.in
> +++ b/linux/Config.in
> @@ -297,6 +297,11 @@ config BR2_LINUX_KERNEL_INSTALL_TARGET
> /boot in the target root filesystem, as is typically done on
> x86/x86_64 systems.
>
> +# This option is used to install firmware to staging. Other packages such as
> +# beagle-capes then install the firmware into the target. This avoids
> +# installing all linux firmware.
I would also states that this applies to special firmware files that are
*not* distributed with the linux-firmware package. All 'standard'
firmwares should be installed via linux-firmware. This knob is for very
special cases such as the BBB capes. Waht about:
# This option can be selected by other packages that require special
# firmwares bundled in some fiorks of the Linux kernell (eg. the BBB
# capes firmwares (.dtbo) as distributed in the TI Linux kernel fork).
# To install other firmwares, please use the linux-firmware package.
> +config BR2_LINUX_KERNEL_INSTALL_FIRMWARE
> + bool
>
> # Linux extensions
> source "linux/Config.ext.in"
> diff --git a/linux/linux.mk b/linux/linux.mk
> index befef16..88c954d 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -256,6 +256,15 @@ define LINUX_INSTALL_KERNEL_IMAGE_TO_TARGET
> endef
> endif
>
> +ifeq ($(BR2_LINUX_KERNEL_INSTALL_FIRMWARE),y)
> +
> +LINUX_INSTALL_STAGING = YES
> +
> +define LINUX_INSTALL_FIRMWARE_TO_STAGING
> + $(TARGET_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(@D) firmware_install \
> + INSTALL_FW_PATH=$(STAGING_DIR)/lib/firmware/
> +endef
> +endif
>
> define LINUX_INSTALL_HOST_TOOLS
> # Installing dtc (device tree compiler) as host tool, if selected
> @@ -269,6 +278,10 @@ define LINUX_INSTALL_IMAGES_CMDS
> cp $(LINUX_IMAGE_PATH) $(BINARIES_DIR)
> endef
>
> +define LINUX_INSTALL_STAGING_CMDS
> + $(LINUX_INSTALL_FIRMWARE_TO_STAGING)
> +endef
> +
> define LINUX_INSTALL_TARGET_CMDS
> $(LINUX_INSTALL_KERNEL_IMAGE_TO_TARGET)
> $(LINUX_INSTALL_DTB)
Otherwise, LGTM.
Peter, Thomas, what do you thiink of this scheme? Should we puruse this
series, or do you have a better idea?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2013-07-08 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 23:31 [Buildroot] [PATCH 1/2] linux: install firmware to staging Spenser Gilliland
2013-07-07 23:31 ` [Buildroot] [PATCH 2/2] beagle-capes: new package Spenser Gilliland
2013-07-08 0:43 ` Frank Hunleth
2013-07-08 3:08 ` Spenser Gilliland
2013-07-08 13:02 ` Frank Hunleth
2013-07-08 17:47 ` Yann E. MORIN
2013-07-09 15:34 ` Spenser Gilliland
2013-07-09 16:07 ` Yann E. MORIN
2013-10-27 11:22 ` Arnout Vandecappelle
2013-10-27 20:43 ` Spenser Gilliland
2013-07-08 17:52 ` Yann E. MORIN [this message]
2013-07-09 10:54 ` [Buildroot] [PATCH 1/2] linux: install firmware to staging Thomas Petazzoni
2013-07-09 14:03 ` Spenser Gilliland
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=20130708175221.GE3206@free.fr \
--to=yann.morin.1998@free.fr \
--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.