From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] beagle-capes: new package
Date: Sun, 27 Oct 2013 12:22:14 +0100 [thread overview]
Message-ID: <526CF766.6070001@mind.be> (raw)
In-Reply-To: <1373239866-18076-2-git-send-email-spenser@gillilanding.com>
On 08/07/13 01:31, Spenser Gilliland wrote:
> installs cape dtbos from the kernel firmware into the target system.
>
> Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
> ---
> package/Config.in | 1 +
> package/beagle-capes/Config.in | 12 ++++++++++++
> package/beagle-capes/beagle-capes.mk | 15 +++++++++++++++
> 3 files changed, 28 insertions(+)
> create mode 100644 package/beagle-capes/Config.in
> create mode 100644 package/beagle-capes/beagle-capes.mk
>
> diff --git a/package/Config.in b/package/Config.in
> index 4df48ba..3b06f98 100644
> --- a/package/Config.in
> +++ b/package/Config.in
> @@ -226,6 +226,7 @@ source "package/rpi-firmware/Config.in"
> source "package/sunxi-boards/Config.in"
> source "package/ux500-firmware/Config.in"
> source "package/zd1211-firmware/Config.in"
> +source "package/beagle-capes/Config.in"
> endmenu
> source "package/freescale-imx/Config.in"
> source "package/acpid/Config.in"
> diff --git a/package/beagle-capes/Config.in b/package/beagle-capes/Config.in
> new file mode 100644
> index 0000000..568e84f
> --- /dev/null
> +++ b/package/beagle-capes/Config.in
> @@ -0,0 +1,12 @@
> +config BR2_PACKAGE_BEAGLE_CAPES
> + bool "beagle-capes"
> + depends on BR2_LINUX_KERNEL && BR2_arm
> + select BR2_LINUX_KERNEL_INSTALL_FIRMWARE
> + help
> + Installs beaglebone capes firmware from the kernel source.
> +
> + This package requires that a kernel with beaglebone capes firmware is
> + selected.
> +
> +comment "requires the linux kernel"
> + depends on !(BR2_LINUX_KERNEL)
> diff --git a/package/beagle-capes/beagle-capes.mk b/package/beagle-capes/beagle-capes.mk
> new file mode 100644
> index 0000000..5b6f121
> --- /dev/null
> +++ b/package/beagle-capes/beagle-capes.mk
> @@ -0,0 +1,15 @@
> +################################################################################
> +#
> +# beagle-capes
> +#
> +################################################################################
> +
> +BEAGLE_CAPES_SOURCE =
> +
> +BEAGLE_CAPES_DEPENDENCIES = linux
> +
> +define BEAGLE_CAPES_INSTALL_TARGET_CMDS
> + $(INSTALL) -m 644 $(STAGING_DIR)/lib/firmware/*.dtbo $(TARGET_DIR)/lib/firmware/
> +endef
Hi Spenser,
We had a discussion at the Buildroot developer meeting, and finally
found a solution which may be better...
Instead of doing the firmware_install from the linux package, you can
do it from the beagle-capes package, i.e.:
define BEAGLE_CAPES_BUILD_CMDS
$(TARGET_MAKE_ENV) $(MAKE) $(LINUX_MAKE_FLAGS) -C $(LINUX_DIR) \
firmware_install INSTALL_FW_PATH=$(@D)
endef
define BEAGLE_CAPES_INSTALL_TARGET_CMDS
$(INSTALL) -m 644 $(@D)/*.dtbo $(TARGET_DIR)/lib/firmware/
endef
We don't expect that this 'install firmware to staging' feature would
ever be used by any other package, that's why we prefer not to have it
in the linux.mk.
By the way, this will only work for a beaglebone-specific kernel, of
course. Is there any way to check for that and error out with a clear error
message?
Regards,
Arnout
> +
> +$(eval $(generic-package))
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-10-27 11:22 UTC|newest]
Thread overview: 14+ 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 [this message]
2013-10-27 20:43 ` Spenser Gilliland
2013-07-08 17:52 ` [Buildroot] [PATCH 1/2] linux: install firmware to staging Yann E. MORIN
2013-07-09 10:54 ` Thomas Petazzoni
2013-07-09 14:03 ` Spenser Gilliland
-- strict thread matches above, loose matches on Subject: below --
2013-07-09 17:00 [Buildroot] [PATCH v2 " Spenser Gilliland
2013-07-09 17:00 ` [Buildroot] [PATCH 2/2] beagle-capes: new package 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=526CF766.6070001@mind.be \
--to=arnout@mind.be \
--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.