[U-Boot] [PATCH] configs: Migrate CONFIG_SYS_TEXT_BASE

[Adam Ford]

On Sat, Feb 3, 2018 at 11:10 AM, Tom Rini <trini at konsulko.com> wrote:
> On the NIOS2 and Xtensa architectures, we do not have
> CONFIG_SYS_TEXT_BASE set.  This is a strict migration of the current
> values into the defconfig and removing them from the headers.
>
> I did not attempt to add more default values in and for now will leave
> that to maintainers.
>
> Signed-off-by: Tom Rini <trini at konsulko.com>
> ---
> What I wonder about, at this point, would be how hard it would be to add
> imply FOO hex/int/str/etc value to the imply keyword.  I don't want to
> see 100 lines worth of default 0xX if Y || Z for CONFIG_SYS_TEXT_BASE as
> that will be unmaintainable.
> ---

[snip]

>           new boards should not use this option.
>
>  config SYS_TEXT_BASE
> -       depends on ARC || X86 || ARCH_UNIPHIER || ARCH_ZYNQMP || \
> -               (M68K && !TARGET_ASTRO_MCF5373L) || MICROBLAZE || MIPS || \
> -               ARCH_ZYNQ || ARCH_KEYSTONE || ARCH_OMAP2PLUS
> +       depends on !NIOS2 && !XTENSA
>         depends on !EFI_APP
> +       default 0x80800000 if ARCH_OMAP2PLUS
>         hex "Text Base"
>         help
> -         TODO: Move CONFIG_SYS_TEXT_BASE for all the architecture
> +         The address in memory that U-Boot will be running from, initially.
>
> -       default 0x80800000 if ARCH_OMAP2PLUS
>

I have a question.  I don't think anything is wrong, but
doc/SPL/README.omap3 shows two different options for
CONFIG_SYS_TEXT_BASE and neither of them are 0x80800000

Option 1 (SPL only):
0x80100000: CONFIG_SYS_TEXT_BASE of U-Boot

Option 2 (SPL or X-Loader):
0x80008000: CONFIG_SYS_TEXT_BASE of U-Boot

I'm sure it's probably been this way for a while, but when reviewing
the omap3_logic board (am/dm37), I noticed it's currenly using
0x80800000, but I am not sure how the rest of the memory map from the
readme applies.  Does this README file need to be updated or deleted?
Will we have any memory conflicts or overlap?


adam


[snip]