Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis_blanchard@mentor.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH] linux: remove the zImage before rebuild
Date: Fri, 17 Jul 2015 11:49:04 -0700	[thread overview]
Message-ID: <55A94E20.2000506@mentor.com> (raw)
In-Reply-To: <20150717194128.7c22974b@free-electrons.com>

On 07/17/2015 10:41 AM, Thomas Petazzoni wrote:
> One thing that we should do is to generalize this appended DTB
> mechanism to make it possible to generate several appended images.
> Currently, since we append to the zImage directly, we cannot generate
> several images, each using a different DTB. By generating to
> zImage.<dtb-name>, we can generate multiple images (and also avoid the
> overwriting problem).

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?

Thanks.

Hollis Blanchard
Mentor Graphics Emulation Division
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150717/ae8ff273/attachment.html>

  reply	other threads:[~2015-07-17 18:49 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 [this message]
2015-07-17 21:16         ` Thomas Petazzoni
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=55A94E20.2000506@mentor.com \
    --to=hollis_blanchard@mentor.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