[U-Boot] [PATCH] tegra2: Change CONFIG_SYS_TEXT_BASE to 0x00108000.

[Stephen Warren]

Thierry Reding wrote at Tuesday, November 15, 2011 11:49 PM:
> * PGP Signed by an unknown key
> 
> * Stephen Warren wrote:
> > Thierry Reding wrote at Tuesday, November 15, 2011 12:19 AM:
> > > NVIDIA's flashing tools assume that the bootloader is loaded at address
> > > 0x00108000. Instead of requiring non-standard builds of those tools
> > > which allow a load address of 0x00E08000, this commit just switches all
> > > Tegra2 boards to use the standard load address.
> >
> > > Note that to successfully boot a standalone U-Boot with this load
> > > address, U-Boot needs to be built with USE_PRIVATE_LIBGCC=yes.
> >
> > Isn't that true irrespective of TEXT_BASE? That's certainly been my
> > experience.
> 
> Yes, but the emphasis is on "standalone" since you can run mainline U-Boot as
> second stage for quickboot/fastboot and 0x00E08000 as load address without
> building with USE_PRIVATE_LIBGCC=yes.

OK. I think it's more just "standalone U-Boot" that "standalone U-Boot
with this load address" then. I think the difference is that when running
as a second stage under fastboot, U-Boot might get loaded on the A9 rather
than the AVP, so the ARM ISA of the AVP doesn't come into play, and Tom
Warren said he thought that USE_PRIVATE_LIBGCC=yes was only needed due
to the AVP's ARM ISA difference.

> The reason for including this in the
> commit message was that it isn't documented anywhere else and I wanted to
> avoid a situation where this question needs to be answered over and over.
> 
> Perhaps the commit message is not the best place, but I would still like to
> have this documented somewhere. Any suggestions?

Can this option be selected by include/configs/tegra2-common.h? I suspect
not since it's more of a make variable. Perhaps it can be forced on by a
Tegra-specific makefile such as arch/arm/cpu/armv7/tegra2/config.mk or
arch/arm/cpu/armv7/tegra2/Makefile? Then it wouldn't need to be documented;
it'd be automatic.

-- 
nvpublic