From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] spl: add overall SPL size check
Date: Sun, 26 May 2019 07:09:37 -0400 [thread overview]
Message-ID: <20190526110937.GV20781@bill-the-cat> (raw)
In-Reply-To: <272edc6e-1a4a-e61a-4990-d38f02218343@gmail.com>
On Fri, May 24, 2019 at 10:10:48PM +0200, Simon Goldschmidt wrote:
> Am 24.05.2019 um 22:07 schrieb Simon Goldschmidt:
> >This adds a size check for SPL that can dynamically check generated
> >SPL binaries (including devicetree) for a size limit that ensures
> >this image plus global data, heap and stack fit in initial SRAM.
> >
> >Since some of these sizes are not available to make, a new host tool
> >'spl_size_limit' is added that dumps the resulting maximum size for
> >an SPL binary to stdout. This tool is used in toplevel Makefile to
> >implement the size check on SPL binaries.
> >
> >Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
> >---
> >
> >Changes in v3:
> >- don't build this new tools for 'make tools-only'
>
> So this is how far I got.
>
> Tom, your idea with making this multi-config aware (U-Boot, SPL and TPL)
> does not seem to work as 'tools' are only built once, not once per
> U-Boot/SPL/TPL. So if we wanted to use this for TPL, too, that would either
> mean create yet another tool or pass an option to this new tool to differ
> between SPL and TPL.
OK. Hopefully at least we can use a Makefile rule to transform the
source code rather than have a copy/paste version of the code. Thanks
again!
--
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/20190526/622bcbe0/attachment.sig>
next prev parent reply other threads:[~2019-05-26 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 20:07 [U-Boot] [PATCH v3] spl: add overall SPL size check Simon Goldschmidt
2019-05-24 20:10 ` Simon Goldschmidt
2019-05-26 11:09 ` Tom Rini [this message]
2019-05-27 13:47 ` Jean-Jacques Hiblot
2019-05-27 14:54 ` Tom Rini
2019-05-27 15:15 ` Simon Goldschmidt
2019-05-28 15:18 ` Jean-Jacques Hiblot
2019-05-28 15:51 ` Simon Goldschmidt
2019-05-27 16:35 ` Masahiro Yamada
2019-05-27 16:48 ` Tom Rini
2019-05-27 19:28 ` Simon Goldschmidt
2019-06-07 22:05 ` 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=20190526110937.GV20781@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