public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] env: don't generate callback list entries for SPL
Date: Mon, 17 Dec 2012 14:12:40 -0500	[thread overview]
Message-ID: <50CF6EA8.4050200@ti.com> (raw)
In-Reply-To: <1355770407.18495.2@snotra>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/17/12 13:53, Scott Wood wrote:
> On 12/17/2012 08:52:59 AM, Tom Rini wrote:
>> On Fri, Dec 14, 2012 at 06:54:05PM -0600, Scott Wood wrote:
>> 
>>> SPL doesn't use the environment.  These list entries prevent
>>> the functions from being garbage-collected, even though nothing
>>> will
>> look at
>>> the list.  This caused several SPL builds (e.g.
>>> P2020RDB-PC_NAND) to break due to size limitations.
>> 
>> SPL with networking support uses the environment, so you need to
>> toss CONFIG_SPL_NET_SUPPORT into the test.  That said, it's not
>> an interactive environment and this might push that area over the
>> size limit too (in the USB case, which is already pretty tight).
> 
> OK, I saw "env_*" stuff in the "ifndef CONFIG_SPL_BUILD" section,
> but later some of it shows up in "ifdef CONFIG_SPL_BUILD" as well.
> 
> So, do you want a v2, or is it OK because it's not interactive?  In
> the latter case should env_callback.o be removed from the SPL
> build?

Lets do a v2 (since the commit message would have been wrong) and add
in a comment saying SPL doesn't have interactive environment, so we
don't need this code.

> Also, env_nvedit.o, env_common.o, and env_flash.o are included for
> SPL regardless of CONFIG_SPL_NET_SUPPORT.  In fact it looks like 
> env_nvedit.o will be included twice if CONFIG_SPL_NET_SUPPORT is 
> enabled. :-P

Since I'd assume 'sort' in make isn't sort -u, I'm not sure how it's
filtering out the dupes unless we don't really need it afterall,
am335x_evm builds with CONFIG_SPL_NET_SUPPORT enabled.  I'm curious
now, so I'm poking it.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQz26oAAoJENk4IS6UOR1WpL0QAJY0PussCOcq+B4Rr2eagtQj
e4glJMGst//JKi8hhGac35QhbyAXIJJDO++QET6PUxItUs+ltPci9884gSfe3wvp
6mSB3UKtKVHhMckcVptOTDhrDqwBCDBUFEPKosONJTYRP0s0vOj3E92bAU+z0CJ4
JyVj94lEvstdNxUKHKxRsxu6PF+okSOb/q9X0efx/boxeuyqPUoT15B0zNrtz4kd
G31Efjy0sP1HrSp73zvSFoVV2N6p+MbKoFJgxM8seRg+JsPRj7DYCnuGn1l/Hj9m
vc+2UMsf9az8+p1333QejYgtFYEmcvrwXXrp4Dcg2e1DCD2mEpmVtCkdI3SFdKvs
CbHUuJ9Uc3CACjo4TtH5V7ZiiDwC8+gsO1ucxmng7/Ezr1XCFLOs4nJZKTUXiqwh
ZBXaGaApBTCi8vClPyH6jYycjgnKIT3R5bcWIjD8ArhpOypy1J3V2/xqqCJhmyzD
gZa1Ym0NXnJ2bSdu2RWcYGyGOt9BLdlpr3nMb03ZdRr2jiy3KktGh2gptDGhz8jk
HQ9IS3jUXEQK4QD+UoKYdNfUSbC3G6e6ISM8otCHDVQO4cef/04bT3sBnvo/oUwD
RiBSxEDE/Gs9m4UHRuroI3bS+bqNjjdmQXSnq39cST3z+y6qMs7TpkN0iHKWoikz
/d7+lr2MD61cneVS5/cj
=kOOU
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-12-17 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-15  0:54 [U-Boot] [PATCH] env: don't generate callback list entries for SPL Scott Wood
2012-12-15  7:04 ` Joe Hershberger
2012-12-17 14:52 ` Tom Rini
2012-12-17 18:53   ` Scott Wood
2012-12-17 19:12     ` Tom Rini [this message]
2012-12-17 19:55       ` Wolfgang Denk
2012-12-17 19:58         ` Tom Rini
2012-12-17 20:11           ` Joe Hershberger

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=50CF6EA8.4050200@ti.com \
    --to=trini@ti.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