From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Building uImage with multiple load addresses
Date: Thu, 22 Dec 2011 05:04:01 +0100 [thread overview]
Message-ID: <201112220504.01444.marek.vasut@gmail.com> (raw)
In-Reply-To: <4EF2792A.5060800@nvidia.com>
> On 12/21/2011 03:20 PM, Fabio Estevam wrote:
> > On Wed, Dec 21, 2011 at 7:24 PM, Fabio Estevam <festevam@gmail.com> wrote:
> >> Hi,
> >>
> >> When trying to build imx_v4_v5_defconfig, or mx3_defconfig, or
> >> mx5_defconfig on a 3.2-rc6 kernel I get:
> >> ...
> >> multiple load addresses: 0x80008000 0x80008000 0x10008000
> >> This is incompatible with uImages
> >> ...
> >> Do I need to do any changes to mkimage?
> >> ...
>
> I'd suggest using "mkimage -t kernel_noload" instead of "mkimage -t
> kernel". That way, you don't have to specify an load/entry address; the
> kernel will be executed wherever you happen to load it in memory, which
> should work fine for an ARM zImage at least.
>
> This feature was introduced pretty recently in mainline U-Boot though,
> so you'll need to build your own new U-boot and mkimage tool.
I think this is fine. And I agree to use this approach. Stephen, I won't be able
to finish the u-boot/zImage support any soon, exams started for me now.
M
next prev parent reply other threads:[~2011-12-22 4:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 21:24 [U-Boot] Building uImage with multiple load addresses Fabio Estevam
2011-12-21 22:20 ` Fabio Estevam
2011-12-22 0:26 ` Stephen Warren
2011-12-22 4:04 ` Marek Vasut [this message]
2011-12-22 8:53 ` Stefano Babic
2011-12-22 9:02 ` Wolfgang Denk
2011-12-22 9:18 ` Stefano Babic
2011-12-22 12:04 ` Wolfgang Denk
2011-12-22 12:31 ` Fabio Estevam
2011-12-22 8:51 ` Stefano Babic
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=201112220504.01444.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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