From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot-wrapper-aarch64: Allow users to specify an initrd/initramfs file.
Date: Tue, 25 Oct 2016 23:57:28 +0200 [thread overview]
Message-ID: <20161025235728.796804cc@free-electrons.com> (raw)
In-Reply-To: <1475880304-21773-2-git-send-email-hollis_blanchard@mentor.com>
Hello,
On Fri, 7 Oct 2016 15:45:03 -0700, Hollis Blanchard wrote:
> Signed-off-by: Hollis Blanchard <hollis_blanchard@mentor.com>
> ---
> boot/boot-wrapper-aarch64/Config.in | 8 ++++++++
> boot/boot-wrapper-aarch64/boot-wrapper-aarch64.mk | 4 ++++
> 2 files changed, 12 insertions(+), 0 deletions(-)
Thanks for your patch, sorry for the somewhat slow reply.
> +config BR2_TARGET_BOOT_WRAPPER_AARCH64_RAMDISK
> + string "Ramdisk"
> + default ""
I would like this option to include the filesystem produced by
Buildroot (in cpio format) as the initramfs. So something like:
bool "Include ramdisk in image"
depends on BR2_TARGET_ROOTFS_CPIO
> + help
> + Embed an initramfs file in the kernel image, and provide
It does not embed the initramfs in the kernel image, but in the boot
wrapper image.
> + linux,initrd-start and linux,initrd-end properties in the /chosen device
> + tree node.
> +
> endif
> diff --git a/boot/boot-wrapper-aarch64/boot-wrapper-aarch64.mk b/boot/boot-wrapper-aarch64/boot-wrapper-aarch64.mk
> index c56bdee..28b2061 100644
> --- a/boot/boot-wrapper-aarch64/boot-wrapper-aarch64.mk
> +++ b/boot/boot-wrapper-aarch64/boot-wrapper-aarch64.mk
> @@ -30,6 +30,10 @@ BOOT_WRAPPER_AARCH64_CONF_OPTS = \
> --with-kernel-dir=$(LINUX_DIR) \
> --with-cmdline=$(BR2_TARGET_BOOT_WRAPPER_AARCH64_BOOTARGS)
>
> +ifneq ($(BR2_TARGET_BOOT_WRAPPER_AARCH64_RAMDISK),)
> + BOOT_WRAPPER_AARCH64_CONF_OPTS += --with-initrd=$(BR2_TARGET_BOOT_WRAPPER_AARCH64_RAMDISK)
Don't indent code inside conditions.
> +endif
It should be something like:
ifeq ($(BR2_TARGET_BOOT_WRAPPER_AARCH64_RAMDISK),y)
BOOT_WRAPPER_AARCH64_CONF_OPTS += --with-initrd=$(BINARIES_DIR)/rootfs.cpio
BOOT_WRAPPER_AARCH64_DEPENDENCIES += rootfs-cpio
endif
or something along those lines.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-25 21:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 22:45 [Buildroot] boot-wrapper-aarch64 configuration options Hollis Blanchard
2016-10-07 22:45 ` [Buildroot] [PATCH] boot-wrapper-aarch64: Allow users to specify an initrd/initramfs file Hollis Blanchard
2016-10-25 21:57 ` Thomas Petazzoni [this message]
2016-10-25 22:28 ` Hollis Blanchard
2017-01-11 23:55 ` Hollis Blanchard
2017-01-12 22:30 ` Arnout Vandecappelle
2017-01-12 22:45 ` Hollis Blanchard
2017-01-13 8:30 ` Arnout Vandecappelle
2016-10-07 22:45 ` [Buildroot] [PATCH] boot-wrapper-aarch64: Allow users to select the PSCI SMP boot method Hollis Blanchard
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=20161025235728.796804cc@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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