public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common/Makefile: Add new symbol CONFIG_SPL_ENV_SUPPORT for environment in SPL
Date: Wed, 22 May 2013 08:09:07 +0200	[thread overview]
Message-ID: <519C6103.3000008@denx.de> (raw)
In-Reply-To: <1369163690.1374.9@scott-Lenovo-G560>

(sorry for jumping in so late in this discussion)

On 05/21/2013 09:14 PM, Scott Wood wrote:
>> This is Tom's words:
>>
>> a3m071 relies on SPL always building cmd_nvedit.o and env_common.o and
>> duplicated CONFIG_ENV_IS_IN_FLASH in the SPL section.
>>
>> CONFIG_SPL_NET_SUPPORT relies on the same always-built ins and adds
>> env_nowhere.o which works because the regular CONFIG_ENV_IS_IN_...
>>
>> section is in the non-SPL-only area.
> 
> If "SPL: Makefile: Build a separate autoconf.mk for SPL" gets merged,  
> we could just have a3m071 define CONFIG_ENV_IS_NOWHERE in the SPL build  
> case.

But the a3m071 SPL U-Boot version also uses the env from NOR flash. So
defining CONFIG_ENV_IS_NOWHERE here would be really confusing!

Thanks,
Stefan

  parent reply	other threads:[~2013-05-22  6:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  3:05 [U-Boot] [PATCH] common/Makefile: Add new symbol CONFIG_SPL_ENV_SUPPORT for environment in SPL ying.zhang at freescale.com
2013-05-17 22:41 ` Scott Wood
2013-05-18  0:58   ` Zhang Ying-B40530
2013-05-20 18:56     ` Scott Wood
2013-05-21  2:43       ` Zhang Ying-B40530
2013-05-21 19:14         ` Scott Wood
2013-05-22  1:52           ` Zhang Ying-B40530
2013-05-22  6:09           ` Stefan Roese [this message]
2013-05-22  8:06             ` Zhang Ying-B40530
2013-05-22 21:22               ` Tom Rini
2013-05-23  2:11                 ` Zhang Ying-B40530
2013-05-22 15:44             ` Scott Wood
2013-05-23  2:24               ` Zhang Ying-B40530

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=519C6103.3000008@denx.de \
    --to=sr@denx.de \
    --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