From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH] linux: remove the zImage before rebuild
Date: Fri, 17 Jul 2015 23:16:32 +0200 [thread overview]
Message-ID: <20150717231632.05928653@free-electrons.com> (raw)
In-Reply-To: <55A94E20.2000506@mentor.com>
Hello,
On Fri, 17 Jul 2015 11:49:04 -0700, Hollis Blanchard wrote:
> A bit of a tangent now, but I am trying to write a recipe for another
> bootwrapper, which prepends a little code to a zImage/DTB combo. Right
> now, it basically boils down to this:
>
> define BOOT_WRAPPER_ARM_BUILD_CMDS
>
> $(MAKE) CROSS_COMPILE=$(TARGET_CROSS) DTBIMAGE=$(BINARIES_DIR)/zImage -C $(@D)
>
> endef
>
>
> Practically speaking, I think the bootwrapper is only really useful in
> the BR2_LINUX_KERNEL_APPENDED_ZIMAGE case, and I can enforce that via
> Kconfig dependencies, so I can assume the kernel name is "zImage".
>
> If your idea above is implemented, would I need to duplicate the
> linux.mk logic around BR2_LINUX_KERNEL_USE_INTREE_DTS,
> BR2_LINUX_KERNEL_INTREE_DTS_NAME, BR2_LINUX_KERNEL_USE_CUSTOM_DTS, and
> BR2_LINUX_KERNEL_CUSTOM_DTS_PATH? Or is there a better way to do this?
We already have a similar case in the boot-wrapper-aarch64 package. I
am indeed not sure how that would work with appended DTB and multiple
zImage generated. Needs some thought, indeed.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-17 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 23:22 [Buildroot] [RFC/PATCH] linux: remove the zImage before rebuild Guido Martínez
2014-10-22 14:40 ` Guido Martínez
2015-03-08 17:47 ` Thomas Petazzoni
2015-03-08 18:53 ` Guido Martínez
2015-07-17 16:01 ` Hollis Blanchard
2015-07-17 16:34 ` Guido Martínez
2015-07-17 17:41 ` Thomas Petazzoni
2015-07-17 18:49 ` Hollis Blanchard
2015-07-17 21:16 ` Thomas Petazzoni [this message]
2015-07-17 21:24 ` 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=20150717231632.05928653@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 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.