Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Guido Martínez" <guido@vanguardiasur.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC/PATCH] linux: remove the zImage before rebuild
Date: Wed, 22 Oct 2014 11:40:35 -0300	[thread overview]
Message-ID: <20141022144035.GA14514@fox> (raw)
In-Reply-To: <1411773774-7712-1-git-send-email-guido@vanguardiasur.com.ar>

Hey Yann,

On Fri, Sep 26, 2014 at 08:22:54PM -0300, Guido Mart?nez wrote:
> Currently, if we run "make linux-rebuild", the device tree blob gets
> appended twice to the kernel image, rendering the latter append useless.

I'm still finding this problem on current BR. I believe it always
happens when one uses an appended DT, but I'm attaching a defconfig that
reproduces it just in case.

You can check that the problem exists by running linux-rebuild and
checking for some DT string.

   $ make
      [...]
   $ strings output/images/uImage | grep am335x-bone
   ti,am335x-bone
   $ make linux-rebuild
      [...]
   $ strings output/images/uImage | grep am335x-bone
   ti,am335x-bone
   ti,am335x-bone

I have a patch that fixes this for the uImage+dt case, but it messes up
some other builds. Likely, to properly fix this, it should be a pretty
invasive change. I think adding a output/build/linux-staging directory
and doing all the DT appends and uImage creation there (without messing
with the kernel tree) would work.

Cheers!

-- 
Guido Mart?nez, VanguardiaSur
www.vanguardiasur.com.ar
-------------- next part --------------
BR2_arm=y
BR2_cortex_a8=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_DEFCONFIG="omap2plus"
BR2_LINUX_KERNEL_APPENDED_UIMAGE=y
BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x80008000"
BR2_LINUX_KERNEL_INTREE_DTS_NAME="am335x-boneblack"

  reply	other threads:[~2014-10-22 14:40 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 [this message]
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
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=20141022144035.GA14514@fox \
    --to=guido@vanguardiasur.com.ar \
    --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