From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Maximum size of u-boot.imx for TBS2910 board
Date: Fri, 6 Dec 2019 09:02:44 -0500 [thread overview]
Message-ID: <20191206140244.GJ9549@bill-the-cat> (raw)
In-Reply-To: <20191206133044.06330a7d@crub>
On Fri, Dec 06, 2019 at 01:30:44PM +0100, Anatolij Gustschin wrote:
> Hi Stefano,
>
> On Fri, 6 Dec 2019 12:41:47 +0100
> Stefano Babic sbabic at denx.de wrote:
> ...
> > I come later to the discussion - anyway, I would like to search for a
> > "pragmatic" solution. I think we can discuss a lot about which code flew
> > in and why tbs2910 increases the size, but I do not know if this brings
> > some results. Several changes (see improvements about fdt handling, and
> > so on) are new features, and it is quite bad to surround any new change
> > with a lot of #ifdef just to fit. We cannot discuss if it is correct or
> > not that boards should switch to DM: this was decided a long time ago
> > and decision won't be changed.
> >
> > We are not talking about big changes in the size: tbs2910 has a low
> > threshold for currrent U-Boot : 392192 and from a build to next build,
> > the size can exceed for "some" bytes. We are not facing a big change,
> > but the board is living on the edge with current U-Boot. I am then quite
> > of Heinrich's opinion, and that the environment should be moved
> > somewhere else to guarantee that board can be supported without fighting
> > any time with the size in future. Soeren has already dropped most of the
> > unused features, and I have no idea if there is something else he can do
> > in this way without dropping used features on the board.
>
> I'm currently looking for ways to slightly reduce image size to convert
> this board to DM_VIDEO. Yesterday I've submitted two patches for video
> uclass, this is still not enough to be able to build the board with
> DM_VIDEO enabled. I'm currently trying to drop dead or useless code from
> mxc_ipuv3 driver and also tried to remove device tree nodes for stuff not
> used in U-Boot. This might give us a few kilobytes of image size reduction
> and DM_VIDEO could probably work (at least when using gcc-8.1). But I'm
> expecting new bloat when next merge window opens and new patches will
> be merged, this board will fail again. Moving the environment would
> help a lot.
I really want to not change the environment as I see it as a reminder
that no, we need to address some of the underlying problems. The
constraints imposed by the platform aren't unreasonable.
That said, I would also be happy to see patches to re-work the buildman
toolchain logic to fetch the appropriate set of "builds something that
works" toolchains as while there are 8.1.0 toolchains from kernel.org we
need at least I believe 8.3 for both all ARM and x86 to work.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191206/62f0d4ad/attachment.sig>
next prev parent reply other threads:[~2019-12-06 14:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 20:09 [U-Boot] Maximum size of u-boot.imx for TBS2910 board Heinrich Schuchardt
2019-11-21 20:12 ` Tom Rini
2019-11-21 21:59 ` Heinrich Schuchardt
2019-11-21 22:01 ` Marek Vasut
2019-11-21 22:45 ` Tom Rini
2019-11-22 0:23 ` Marek Vasut
2019-11-22 0:32 ` Tom Rini
2019-11-22 1:27 ` Marek Vasut
2019-11-22 1:30 ` Tom Rini
2019-11-22 1:38 ` Marek Vasut
2019-11-22 2:53 ` Tom Rini
2019-11-22 2:56 ` Marek Vasut
2019-11-22 3:41 ` Tom Rini
2019-11-22 3:58 ` Marek Vasut
2019-11-22 10:29 ` Soeren Moch
2019-11-22 11:42 ` Heinrich Schuchardt
2019-11-22 12:30 ` Tom Rini
2019-11-22 12:18 ` Marek Vasut
2019-12-06 11:41 ` Stefano Babic
2019-12-06 12:30 ` Anatolij Gustschin
2019-12-06 14:02 ` Tom Rini [this message]
2019-12-06 16:18 ` Soeren Moch
2019-12-06 16:43 ` Soeren Moch
2019-11-22 15:44 ` Tom Rini
2019-11-22 18:31 ` Marek Vasut
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=20191206140244.GJ9549@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