[U-Boot] [PATCH] arm: Add option to disable code relocation
Graeme Russ
graeme.russ at gmail.com
Wed Feb 8 00:28:42 CET 2012
Hi Wolfgang,
On Wed, Feb 8, 2012 at 10:23 AM, Wolfgang Denk <wd at denx.de> wrote:
> Dear Dirk Behme,
>
> In message <4F30C794.50206 at de.bosch.com> you wrote:
>>
>> > Also, if SPL can determine total SDRAM, copy U-Boot to the final location
>> > and perform the relocations, there is no need for relocation to be done by
>> > U-Boot. As I understand it, SPL loads U-Boot into a fixed address and then
>> > U-Boot copies itself to top-of-RAM. We can save one copy
>>
>> Yes, exactly, saving this one copy was the the reason for me to start
>> this thread.
>
> Is nobody _reading_ what I try to explain again and again and again?
>
> If SPL was to determing the relocation address, it would also have to
> read the environment, because there are a number of environment
> variables which can cause (dynamically) the relocation address to
> change.
But this is not neccessarily the case for every board (or even every arch)
For those boards/arches which CAN calculate the relocation address (either
because it is fixed do to npn-variable RAM size, or fixed in relation to
the maximum RAM address) why should we prohibit a method of skipping the
redundant copy operation in a way which is 100% transparent to everyone
else?
Regards,
Graeme
More information about the U-Boot
mailing list