From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 3/4] configs: define CONFIG_SPL_SIZE_LIMIT
Date: Fri, 7 Jun 2019 20:38:21 -0400 [thread overview]
Message-ID: <20190608003821.GG7461@bill-the-cat> (raw)
In-Reply-To: <CAOMZO5DAcvkOab6UF1fTOs2XHTC9-+pnKB+Okhu=BzvbXtGL-Q@mail.gmail.com>
On Fri, Jun 07, 2019 at 07:13:47PM -0300, Fabio Estevam wrote:
> Hi Tom and Heinrich,
>
> On Fri, Jun 7, 2019 at 7:06 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Tue, Apr 02, 2019 at 07:19:06PM +0200, Heinrich Schuchardt wrote:
> >
> > > A new configuration variable CONFIG_SPL_SIZE_LIMIT is introduced to define
> > > the board specific maximum size for the SPL file.
> > >
> > > Use Makefile function size_check() to implement the test.
> > >
> > > Depending on the size of CONFIG_SPL_SIZE_LIMIT an error like the following
> > > is thrown:
> > >
> > > spl/u-boot-spl.bin exceeds file size limit:
> > > limit: 30720 bytes
> > > actual: 33426 bytes
> > > excess: 2706 bytes
> > > make: *** [Makefile:1663: spl/u-boot-spl.bin] Error 1
> > >
> > > Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
> >
> > Applied to u-boot/master, thanks!
>
> Just tested this on mx6sabresd_defconfig, where the SPL size limit is
> 68 * 1024, so I passed:
>
> CONFIG_SPL_SIZE_LIMIT=69632
>
> but SPL builds without error and the generated size is 76800.
>
> Any ideas why CONFIG_SPL_SIZE_LIMIT did not catch the SPL size
> overflow for mx6sabresd_defconfig?
So, I hit this too. SPL_SIZE_LIMIT is hex, not int. Or rather, Simon's
patch changes it from int to hex, which, yeah, that's wrong. Thanks for
the report, patch coming up!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190607/c156ec04/attachment.sig>
next prev parent reply other threads:[~2019-06-08 0:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 17:19 [U-Boot] [PATCH v4 0/4] configs: rk3288: Tinker Board SPL file must fit into 32 KiB Heinrich Schuchardt
2019-04-02 17:19 ` [U-Boot] [PATCH v4 1/4] Makefile: reusable function for BOARD_SIZE_CHECK Heinrich Schuchardt
2019-06-07 22:04 ` Tom Rini
2019-04-02 17:19 ` [U-Boot] [PATCH v4 2/4] imx: move BOARD_SIZE_CHECK to main Makefile Heinrich Schuchardt
2019-04-04 20:53 ` Heinrich Schuchardt
2019-04-05 13:05 ` Fabio Estevam
2019-04-07 21:10 ` Heinrich Schuchardt
2019-06-07 22:04 ` Tom Rini
2019-04-02 17:19 ` [U-Boot] [PATCH v4 3/4] configs: define CONFIG_SPL_SIZE_LIMIT Heinrich Schuchardt
2019-06-07 22:05 ` Tom Rini
2019-06-07 22:13 ` Fabio Estevam
2019-06-08 0:38 ` Tom Rini [this message]
2019-04-02 17:19 ` [U-Boot] [PATCH v4 4/4] configs: rk3288: Tinker Board SPL file must fit into 32 KiB Heinrich Schuchardt
2019-06-07 22:05 ` Tom Rini
2019-04-02 17:29 ` [U-Boot] [PATCH v4 0/4] " Tom Rini
2019-04-02 17:33 ` Heinrich Schuchardt
2019-04-02 17:47 ` Tom Rini
2019-04-02 18:17 ` Heinrich Schuchardt
2019-04-02 18:08 ` Simon Goldschmidt
2019-04-03 0:59 ` Kever Yang
2019-04-03 6:19 ` Heinrich Schuchardt
2019-04-03 20:50 ` Benoît Thébaudeau
2019-04-18 20:12 ` Simon Goldschmidt
2019-04-22 14:36 ` Tom Rini
2019-04-22 18:40 ` Simon Goldschmidt
2019-04-22 19:29 ` Tom Rini
2019-04-22 19:50 ` Simon Goldschmidt
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=20190608003821.GG7461@bill-the-cat \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox