From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] tools: fix FIT image with ramdisk
Date: Sat, 13 Jul 2013 16:02:42 -0400 [thread overview]
Message-ID: <51E1B262.3060001@ti.com> (raw)
In-Reply-To: <20130713112153.98D2E381200@gemini.denx.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/13/2013 07:21 AM, Wolfgang Denk wrote:
> Dear Tom Rini,
>
> In message <20130712212416.GV13531@bill-the-cat> you wrote:
>>
>> A FIT image with a ramdisk that sets the entry or load points to
>> 0x0 must be treated as meaning "leave in place" and NOT "relocate
>> to 0x0".
>
> Why is this the case? 0x0 could be a valid address on some
> systems. If we need a special address that "cannot exist", we
> should rather use the last address in the addressable range (i. e.
> (void *)(~0)).
True enough, but we're not back to the behaviour of the previous
release. In fact, this makes me wonder if there's not a solution to
the problem I had before of wanting to just leave everything in-place
(so that we could have a FIT image with an ARM multi-platform kernel
that would be usable on multiple platforms without multiple copies of
the zImage).
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJR4bJiAAoJENk4IS6UOR1WMbgP/jNjjMJbAPNBLTlyPGPZxK92
K2tBEXezsaWV53MGVTaHt6ZcrpOhSo7j2DP7lO0/j9nH5TM9mJ6tWDKzZxaopMoT
chyyDEN38IaY1LiklwqwyHj8tOCIbCGLtaG0vplHeodE8UFgmBU4QMpBqVvwBids
vtNAjQy0MHI5LXDTY0OpVNzVIQD2Rm2y3xyPnRsuUWoY5BtGmcxs1X5KyoCKbQ3J
qtG0Eb2nP2fuADSgOOTtA1CQRKrKoSk7k2r8fVPzZ85S+8goro8n+a7AgWhuvU+C
WrGKxrlejbUejh7JZt0HGpNr1iIos+7+V3G5PP8pel4JOkaD/jdBgf4UgN2sADXM
JKvkd65jiIRvW4Axw+tZ8omHzXRYPYNe6wgH9CKDtUbSWnRVdvXvtF78XEIMi1XX
iDOAZVca+3qsrx0hJTc34++C2rBsONa5Yd88GwsNwb9BZufqs+uyhD0N19xBqjFC
pd9cJwKuL1P7T7IEHP5N1anerJPNfUCtvZv5RnWKzZBGpvjfZUeZ2PcS2/nuXEHZ
rj3jX9PvzGO1L/mgYCMQ39/6zH5Wge70ojbMkn/Lh+cWWZb4Y7LuUfGINH/XTjrb
H+/OQ2RuDPje04X6e3ws1vAXwy8NF8mltcLwnusKkcqf3VhhTHoOOm/OHyjTLw5a
tf4c94PHN023tdpUtsR1
=G4tN
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-07-13 20:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 13:09 [U-Boot] [PATCH] tools: fix FIT image with ramdisk Stefano Babic
2013-07-12 13:20 ` Albert ARIBAUD
2013-07-12 21:24 ` Tom Rini
2013-07-13 7:17 ` Albert ARIBAUD
2013-07-13 9:33 ` Stefano Babic
2013-07-13 11:21 ` Wolfgang Denk
2013-07-13 20:02 ` Tom Rini [this message]
2013-07-14 2:26 ` Stephen Warren
2013-07-14 2:55 ` Tom Rini
2013-07-20 22:06 ` Simon Glass
2013-07-20 22:38 ` Tom Rini
2013-07-20 23:29 ` Simon Glass
2013-07-20 23:36 ` Tom Rini
2013-08-13 13:53 ` Tom Rini
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=51E1B262.3060001@ti.com \
--to=trini@ti.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