[PATCH 0/4] bootm: Handle compressed arm64 images with bootm

[Simon Glass]

Hi Rasmus,

On Tue, 7 Nov 2023 at 02:56, Rasmus Villemoes
<rasmus.villemoes at prevas.dk> wrote:
>
> On 05/11/2023 21.03, Simon Glass wrote:
> > This little series corrects a problem I noticed with arm64 images,
> > where the kernel is not recognised:
>
> The $subject is misleading, bootm works just fine with compressed arm64
> images, with the type set to "kernel".
>
> >         Type:         Kernel Image (no loading done)
> >         Compression:  gzip compressed
>
> Isn't that a non-sensical combination to begin with? Decompressing the
> Image.gz kernel image to any location (however you determine that
> destination) _is_ loading it.

Yes, I agree.

>
> If you want XIP, obviously the image must be uncompressed in the FIT. I
> don't understand what you're trying to do here.

Hmmm, I think I have just got confused about all of this, perhaps
because ChromeOS uses kernel_noload with compression. Is that an
invalid combination?

But then how does loading actually work? We don't want to put the load
address in the FIT, since we don't know what it is...we want to use
the address provided by the board. Which is kernel_noload...so how
should this be implemented?

Regards,
Simon