From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: U-Boot Mailing List <u-boot@lists.denx.de>,
Marek Vasut <marex@denx.de>, Eddie James <eajames@linux.ibm.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Mattijs Korpershoek <mkorpershoek@baylibre.com>,
Safae Ouajih <souajih@baylibre.com>
Subject: Re: [PATCH 2/4] bootm: Move arm64-image processing later
Date: Sun, 5 Nov 2023 16:20:14 -0500 [thread overview]
Message-ID: <20231105212014.GF496310@bill-the-cat> (raw)
In-Reply-To: <20231105130351.2.Ie34b75c75347a1c04bffa780220afe9011b0e2bb@changeid>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
On Sun, Nov 05, 2023 at 01:03:52PM -0700, Simon Glass wrote:
> If the image is compressed, then the existing check fails, since the
> header is wrong.
>
> Move the check later in the boot process, after the kernel is
> decompressed. This allows use of bootm with compressed kernels, while
> still permitting an uncompressed kernel to be used.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
How are we getting in to this case exactly?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-11-05 21:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 20:03 [PATCH 0/4] bootm: Handle compressed arm64 images with bootm Simon Glass
2023-11-05 20:03 ` [PATCH 1/4] bootm: Allow ignoring the load address with kernel_noload Simon Glass
2023-11-05 21:19 ` Tom Rini
2023-11-06 17:25 ` Simon Glass
2023-11-06 18:30 ` Tom Rini
2023-11-06 19:58 ` Simon Glass
2023-11-06 20:15 ` Tom Rini
2023-11-07 1:09 ` Simon Glass
2023-11-05 20:03 ` [PATCH 2/4] bootm: Move arm64-image processing later Simon Glass
2023-11-05 21:20 ` Tom Rini [this message]
2023-11-06 17:25 ` Simon Glass
2023-11-05 20:03 ` [PATCH 3/4] image: Show the load address when decompressing Simon Glass
2023-11-05 20:03 ` [PATCH 4/4] image: Correct load_bug typo Simon Glass
2023-11-05 20:06 ` [PATCH 0/4] bootm: Handle compressed arm64 images with bootm Simon Glass
2023-11-07 9:56 ` Rasmus Villemoes
2023-11-07 12:23 ` Simon Glass
2023-11-07 13:04 ` Tom Rini
2023-11-07 13:31 ` Simon Glass
2023-11-07 13:49 ` Tom Rini
2023-11-07 14:30 ` Simon Glass
2023-11-07 19:04 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231105212014.GF496310@bill-the-cat \
--to=trini@konsulko.com \
--cc=eajames@linux.ibm.com \
--cc=ilias.apalodimas@linaro.org \
--cc=marex@denx.de \
--cc=mkorpershoek@baylibre.com \
--cc=sjg@chromium.org \
--cc=souajih@baylibre.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.