From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] mpc83xx: New board support SIMPC8313
Date: Tue, 25 Nov 2008 11:02:12 -0600 [thread overview]
Message-ID: <492C2F94.20005@freescale.com> (raw)
In-Reply-To: <20081124183714.07cf1670.kim.phillips@freescale.com>
Kim Phillips wrote:
> On Fri, 21 Nov 2008 16:44:18 -0800 (PST)
> Ron Madrid <ron_madrid@sbcglobal.net> wrote:
>> This would allow for more board specific nand_spl boot code.
>> Would something like this be allowed or am I barking up the
>> wrong tree?
>
> I'd rather we find stuff that can be ifdeffed out or moved elsewhere -
That's great if it's possible, but it's a very tight image and we're
currently wasting 1/16 of it.
> the moment we move something in there, someone will find the need to
> enhance and grow whatever moved there.
So put something in there that is unlikely to grow, and if it does grow,
swap it with something else. I think you've gotten spoiled by the lack
of resource constraints. :-)
> what was the 4.2 toolchain doing differently than the 4.1 toolchain?
> maybe that's an area worth looking into.
Agreed, code size regressions with -Os should warrant a bug report.
-Scott
next prev parent reply other threads:[~2008-11-25 17:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 0:44 [U-Boot] [PATCH v3] mpc83xx: New board support SIMPC8313 Ron Madrid
2008-11-25 0:37 ` Kim Phillips
2008-11-25 17:02 ` Scott Wood [this message]
2008-11-25 19:11 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2008-11-20 22:33 Ron Madrid
2008-11-15 1:13 Ron Madrid
2008-11-20 0:15 ` Kim Phillips
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=492C2F94.20005@freescale.com \
--to=scottwood@freescale.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.