From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Sat, 13 Jul 2013 20:26:33 -0600
Subject: [U-Boot] [PATCH] tools: fix FIT image with ramdisk
In-Reply-To: <20130713112153.98D2E381200@gemini.denx.de>
References: <1373634563-9446-1-git-send-email-sbabic@denx.de>
	<20130712212416.GV13531@bill-the-cat>
	<20130713112153.98D2E381200@gemini.denx.de>
Message-ID: <51E20C59.6040708@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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?