From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] linux: Fix uImage with appended DTs generation
Date: Thu, 1 Aug 2013 18:00:36 +0200 [thread overview]
Message-ID: <20130801180036.79e8cee1@skate> (raw)
In-Reply-To: <1370611303-5054-1-git-send-email-maxime.ripard@free-electrons.com>
Dear Maxime Ripard,
On Fri, 7 Jun 2013 15:21:43 +0200, Maxime Ripard wrote:
> Fixes bug #5516 - appended device tree blobs on uImage fails
>
> Before version 3.7 of the kernel, building the zImage and then the
> uImage will rewrite the zImage in the process, removing the device tree
> we just appended.
>
> Use mkimage to append the device tree to the uImage and rebuild the
> headers directly.
>
> Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
> ---
> linux/linux.mk | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
Applied, thanks.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-08-01 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 13:21 [Buildroot] [PATCHv2] linux: Fix uImage with appended DTs generation Maxime Ripard
2013-06-24 9:34 ` Maxime Ripard
2013-08-01 16:00 ` Thomas Petazzoni [this message]
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=20130801180036.79e8cee1@skate \
--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