[U-Boot] [PATCH] tools: fix FIT image with ramdisk

Tom Rini
2013-07-14T02:55:52Z

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/13/2013 10:26 PM, Stephen Warren wrote:
> On 07/13/2013 05: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)).
>
> For the kernel, we created a special image type for "no
> relocation"; IH_TYPE_KERNEL_NOLOAD. Is an equivalent needed to the
> initrd?

No, because what we have today is insufficient for the kernel, you
still have to specify the load/entry point, in FIT at least, even on
NOLOAD. I'd have sworn at least, I couldn't find a way to get around
this problem before...

- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJR4hM4AAoJENk4IS6UOR1WKOUP/1IVfyWujtl1d5EIqLWRbaRe
BxkIafbsWE8MgmGHtDLhy/snJqHvi57Bs/egkV+mrhfOYmQIjYWOylKCyRhIXW/7
s+b0fLqo5y5fMjdtANdHIU0Jp6j7tkT+dIkU5SPWsGp38uHTDhP9TuDtwHtF4Brm
uMhdxCT72x+VzyzwsUXRj0BY5LhJJULmOEHTm0t40Gs3wNCKx/SQKKOrNGwLH9n9
VzLlPZGX8ABKHdEcSjGExEJ1vXV5ulvKFKhUkSURoM0R9qG3/Esvw4nsnkLiobEK
Bh1Ja6jX9uGR2afUS8JSgem6SYl/8wnBvNGMjWHR5gPNeY4Ujhv/Q4fc2qYhIJTa
qHIZb+lMSlQCe7qBD3JaTeGfuPIQfVgLDQqqrLNKLLr47me8Vw8gMDf3PK9lKuwd
8H7zTlMvdUM3he+QrI4capLSmfYzNkgmfK2HC/V3aswJ38eJUrw/jIRRz4py/biK
E1gz0dCAbVvlh7waN72szapFsZXT6/2bqLg1HQQM6H/Hsf18fA8XxkVCO7C29HJo
1e90TV0DYJ5qENWY6BFyI7B+f6wtWx0JP23tlcmEciag/nwd6TkSaf03X8mDKlhY
yRs56ejWpogg/T5PIjj/L332yVwPuzsvZTWGTtAsV+C2V2xu7oo3esgvLzDbBmXO
rXuYrHDKoRQ5+jnBE1aa
=dxLu
-----END PGP SIGNATURE-----