[PATCH v7 1/4] spl: remove usage of CMD_BOOTx from image parsing

Simon Glass sjg at chromium.org
Thu Apr 17 23:37:40 CEST 2025


Hi Anshul,

On Thu, 17 Apr 2025 at 14:58, Tom Rini <trini at konsulko.com> wrote:
>
> On Tue, Apr 08, 2025 at 07:44:30PM +0530, Anshul Dalal wrote:
>
> > Using CMD_* configs from spl doesn't make logical sense. Therefore this
> > patch replaces the checks for CMD_BOOTx with newly added library symbols
> > BOOTI, BOOTM and BOOTZ which are enabled by their respective CMD_* or
> > SPL_* counterparts.
> >
> > SPL_BOOTZ is enabled by default for 32-bit ARM systems and SPL_BOOTI is
> > enabled by default for 64-bit ARM and RISCV.
> >
> > The respective C files (image.c/zimage.c) are compiled based on library
> > symbols BOOTx instead which are in turn selected by both CMD_BOOTx and
> > SPL_BOOTx as required.
> >
> > Signed-off-by: Anshul Dalal <anshuld at ti.com>
>
> So, for the series, we have a few problems, still. First, this is still
> not size neutral as we now end up dropping bootz from a few 32bit
> platforms (gwventana_nand, display5, gwventana_emmc, display5_factory)
> and growing colibri_vf. Next and more importantly, as after Nishanth's
> explanation, TF-A isn't going to support this case either, I believe
> it's best to just drop this part of the support as well. Thanks for the
> effort all the same.

With the size issues resolved this patch is a good step forward
towards being able to entirely disable CMDLINE in U-Boot and boot with
standard boot:

Reviewed-by: Simon Glass <sjg at chromium.org>

Regards,
Simon


More information about the U-Boot mailing list