[U-Boot] [PATCH] common/Makefile: Add new symbol CONFIG_SPL_ENV_SUPPORT for environment in SPL

[Zhang Ying-B40530]

-----Original Message-----
From: Wood Scott-B07421 
Sent: Wednesday, May 22, 2013 3:15 AM
To: Zhang Ying-B40530
Cc: Wood Scott-B07421; u-boot at lists.denx.de; afleming at gmail.com; Xie Xiaobo-R63061; tom.rini at gmail.com
Subject: Re: [PATCH] common/Makefile: Add new symbol CONFIG_SPL_ENV_SUPPORT for environment in SPL

On 05/20/2013 09:43:53 PM, Zhang Ying-B40530 wrote:
> 
> 
> 
> 
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: Tuesday, May 21, 2013 2:56 AM
> To: Zhang Ying-B40530
> Cc: Wood Scott-B07421; u-boot at lists.denx.de; afleming at gmail.com; Xie
> Xiaobo-R63061; Tom Rini
> Subject: Re: [PATCH] common/Makefile: Add new symbol
> CONFIG_SPL_ENV_SUPPORT for environment in SPL
> 
> 
> I'm not that familiar with CONFIG_SPL_NET_SUPPORT, but it looks like
> it
> 
> just enables the net/ directory in an SPL.  How does that conflict
> with
> 
> env stuff?  Perhaps there's some other symbol that better describes
> the
> 
> actual conflict.
> 
> [Zhang Ying]
> 
> 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.
[Zhang Ying] 
So far I haven't seen it. What should I do?