[U-Boot] [PATCH 2/4] Use LINK_OFF to access global data

[Scott Wood <scottwood@freescale.com>]

Joakim Tjernlund wrote:
> 
> u-boot-bounces at lists.denx.de wrote on 05/01/2010 21:20:32:
> 
>> From: Scott Wood <scottwood@freescale.com>
>> To: Albert ARIBAUD <albert.aribaud@free.fr>
>> Cc: u-boot at lists.denx.de
>> Date: 05/01/2010 21:22
>> Subject: Re: [U-Boot] [PATCH 2/4] Use LINK_OFF to access global data
>> Sent by: u-boot-bounces at lists.denx.de
>>
>> On Sun, Jan 03, 2010 at 09:06:51PM +0100, Albert ARIBAUD wrote:
>>> Hmm... PIC is interesting only if you want the same binary to run from
>>> two places, like NOR then RAM, which is the case when U-boot is the code
>>> which gets run in NOR at power-up and ends up running in RAM later.
>>>
>>> For NAND-based boards, the NAND bootloader will load U-boot to RAM, and
>>> U-boot will never run from anywhere else but its intended RAM location.
>> Note that the first-stage NAND loader still needs to be able to relocate
>> itself to RAM in order to free up the NAND buffer for loading more data.
> 
> Hmm, does that mean that the LINK_OFF patches are useful to you or not?

I was just responding to a suggestion that a split similar to the NAND 
loader might eliminate the need for relocation/PIC support.

I am a bit nervous about this stuff, though -- why is it needed?  We 
just got rid of the need for manual relocations, and now we're adding 
them back (pre-reloc instead of post-reloc). :-(

-Scott