From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Carlo Caione" <ccaione@baylibre.com>
Cc: <u-boot@lists.u-boot-project.org>,
"Jonas Karlman" <jonas@kwiboo.se>, "E Shattow" <e@freeshell.de>
Subject: Re: [PATCH v4 0/5] Add fastboot to SPL
Date: Fri, 21 Aug 2026 08:21:30 -0400 [thread overview]
Message-ID: <jwva4qf7kuq.fsf-monnier+Inbox@gnu.org> (raw)
In-Reply-To: <DKUFJ6TTK7AW.2VKPRV8CRQ70V@baylibre.com>
Carlo Caione [2026-08-21 09:05:37] wrote:
> It is possible to include U-Boot proper in the host-loaded bootstrap
> and use its existing fastboot implementation. That is a valid approach
> and is preferable where the Boot ROM download limit and memory budget
> allow it.
Right, that's the situation I'm familiar with.
> But it is not always possible: some platforms (like the one we are
> enabling) impose a strict size limit on the bootstrap, or only provide
> enough early memory for the DDR initialization code and (small)
> SPL-sized payload.
I associate "fastboot" with the Android nebula, so I find it hard to
imagine a machine with enough resources to run Android yet with a small
enough boot memory for U-Boot not to fit into it. I assume the SPL is
pre-installed in some dedicated boot memory (SPI NOR?) whereas the main
storage is left uninitialized during production. And the NOR flash is
so small that it can't even accommodate a proper U-Boot?
I wonder how many cents it saves the manufacturer (e.g. compared to
having a slightly bigger NOR, or not having the NOR at all and
pre-installing U-Boot on the main storage) 🙁
Anyway, this is clearly getting offtopic. Thanks for the answer.
=== Stefan
next prev parent reply other threads:[~2026-08-21 13:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260820-ccaione-upstream-spl-fastboot-v4-0-57e5ef71c74d__17726.0234997206$1787249364$gmane$org@baylibre.com>
2026-08-20 18:50 ` [PATCH v4 0/5] Add fastboot to SPL Stefan Monnier
2026-08-21 4:05 ` E Shattow
2026-08-21 7:05 ` Carlo Caione
2026-08-21 12:21 ` Stefan Monnier [this message]
2026-08-21 16:13 ` Carlo Caione
2026-08-20 18:08 Carlo Caione
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=jwva4qf7kuq.fsf-monnier+Inbox@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ccaione@baylibre.com \
--cc=e@freeshell.de \
--cc=jonas@kwiboo.se \
--cc=u-boot@lists.u-boot-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox