From: Philip Oberfichtner <pro@denx.de>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, Anshul Dalal <anshuld@ti.com>,
Dario Binacchi <dario.binacchi@amarulasolutions.com>,
Greg Malysa <malysagreg@gmail.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Jerome Forissier <jerome.forissier@linaro.org>,
Marek Vasut <marex@denx.de>,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Paul Kocialkowski <contact@paulk.fr>, Peng Fan <peng.fan@nxp.com>,
Peter Robinson <pbrobinson@gmail.com>,
Simon Glass <sjg@chromium.org>
Subject: Re: [PATCH v4 1/3] Makefile: Add size check for u-boot-with-spl.bin
Date: Wed, 30 Jul 2025 14:41:07 +0200 [thread overview]
Message-ID: <aIoS41wCbNrZyLHm@antares> (raw)
In-Reply-To: <20250729142211.GK1807455@bill-the-cat>
On Tue, Jul 29, 2025 at 08:22:11AM -0600, Tom Rini wrote:
> On Tue, Jul 29, 2025 at 02:27:49PM +0200, Philip Oberfichtner wrote:
> > Hi Tom,
> >
> > On Mon, Jul 28, 2025 at 04:25:31PM -0600, Tom Rini wrote:
> > > On Tue, Jul 08, 2025 at 12:39:57PM +0200, Philip Oberfichtner wrote:
> > >
> > > > Like other images, u-boot-with-spl.bin may be subject to size
> > > > restrictions. Extend CONFIG_SPL_SIZE_LIMIT to handle this case.
> > > >
> > > > Signed-off-by: Philip Oberfichtner <pro@denx.de>
> > > > ---
> > > >
> > > > Notes:
> > > > Changes in v4: none
> > > >
> > > > Changes in v3:
> > > > Reuse existing SPL_SIZE_LIMIT instead of implementing a new option
> > > >
> > > > Changes in v2: none
> > > >
> > > > Makefile | 1 +
> > > > common/spl/Kconfig | 2 +-
> > > > 2 files changed, 2 insertions(+), 1 deletion(-)
> > >
> > > This is not quite right enough, sorry. This causes a number of boards
> > > (evb-ast2600 ibm-sbp1 stm32746g-eval_spl stm32f746-disco_spl
> > > stm32f769-disco_spl) which have size checks and are fine to now fail
> > > their size checks, presumably because they're checking the "wrong" file
> > > now or similar.
> >
> > Thanks for pointing that out. To sum it up: If those boards use
> > SPL_SIZE_LIMIT to restrict the size of an SPL-only image, then
> > u-boot-with-spl.bin, of course, can be too large and the build fails.
> >
> > Plus in our previous discussion, we figured out why using
> > BOARD_SIZE_LIMIT also isn't suitable:
> > https://lore.kernel.org/u-boot/aD2EflR9DRYG-MY5@antares/
> >
> > So from here I really don't see any better way than introducing yet
> > another CONFIG_*SIZE_LIMIT option.
> >
> >
> > But maybe we can however simplify and deduplicate some of the code. What
> > do you think about something like that (I have not yet tested it, just
> > a rough idea so far):
>
> That sounds like a good idea, so long as it works :) Thanks!
>
So I've tested it for multiple board/image combinations. Should be fine
now. v5 is on the way.
Best regards,
Philip
> --
> Tom
--
=====================================================================
DENX Software Engineering GmbH,
Managing Director: Johanna Denk, Tabea Lutz
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
=====================================================================
next prev parent reply other threads:[~2025-07-30 12:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 10:39 [PATCH v4 0/3] Add Onion Omega2/2+ board support Philip Oberfichtner
2025-07-08 10:39 ` [PATCH v4 1/3] Makefile: Add size check for u-boot-with-spl.bin Philip Oberfichtner
2025-07-08 11:31 ` Ilias Apalodimas
2025-07-08 14:34 ` Philip Oberfichtner
2025-07-10 8:32 ` Ilias Apalodimas
2025-07-28 22:25 ` Tom Rini
2025-07-29 12:27 ` Philip Oberfichtner
2025-07-29 14:22 ` Tom Rini
2025-07-30 12:41 ` Philip Oberfichtner [this message]
2025-07-08 10:39 ` [PATCH v4 2/3] mips: serial: Silence "unused variable" warning Philip Oberfichtner
2025-07-08 10:39 ` [PATCH v4 3/3] mips: mt7628: Add Onion Omega2/2+ board support Philip Oberfichtner
2025-07-17 8:04 ` [PATCH v4 0/3] " Philip Oberfichtner
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=aIoS41wCbNrZyLHm@antares \
--to=pro@denx.de \
--cc=anshuld@ti.com \
--cc=contact@paulk.fr \
--cc=dario.binacchi@amarulasolutions.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jerome.forissier@linaro.org \
--cc=malysagreg@gmail.com \
--cc=marex@denx.de \
--cc=nathan.morrison@timesys.com \
--cc=pbrobinson@gmail.com \
--cc=peng.fan@nxp.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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.