[PATCH 2/2] ARM: axxia: remove TEXT_OFFSET override hack

[Ard Biesheuvel]

On Tue, 12 Jan 2021 at 11:34, Alexander Sverdlin
<alexander.sverdlin at nokia.com> wrote:
>
> Hi Ard!
>
> On 11/01/2021 11:30, Ard Biesheuvel wrote:
> > Now that the decompressor will take memreserve entries into account when
> > placing the uncompressed kernel in memory on DT platforms, we no longer
> > have to override TEXT_OFFSET to stay clear of the memory reservation that
> > exists at the base of memory on these platforms.
> >
> > Signed-off-by: Ard Biesheuvel <ardb at kernel.org>
> > ---
> >  arch/arm/Makefile | 1 -
> >  1 file changed, 1 deletion(-)
> >
> > diff --git a/arch/arm/Makefile b/arch/arm/Makefile
> > index 4aaec9599e8a..c0496983198f 100644
> > --- a/arch/arm/Makefile
> > +++ b/arch/arm/Makefile
> > @@ -151,7 +151,6 @@ textofs-$(CONFIG_ARCH_IPQ40XX) := 0x00208000
> >  textofs-$(CONFIG_ARCH_MSM8X60) := 0x00208000
> >  textofs-$(CONFIG_ARCH_MSM8960) := 0x00208000
> >  textofs-$(CONFIG_ARCH_MESON) := 0x00208000
> > -textofs-$(CONFIG_ARCH_AXXIA) := 0x00308000
> >
> >  # Machine directory name.  This list is sorted alphanumerically
> >  # by CONFIG_* macro name.
>
> What should the users of uncompressed kernel do with their legacy bootloaders?
> I've tested you patch and AXXIA bootloader is not able to deal with 0x8000 default
> load address...
>

I am not sure I understand why this makes a difference. Does the AXXIA
bootloader take the load address from the uncompressed image somehow?

I would assume that the bootloader knows about the memory reservation
at the base of DRAM, and places the kernel image outside of it. That
kernel image can now run at any offset of the start of DRAM modulo 2
MB.

Maybe the issue is that the old offset is 3 MiB?