-----Original Message----- From: Wood Scott-B07421 Sent: Wednesday, May 22, 2013 11:45 PM To: Stefan Roese Cc: Zhang Ying-B40530; Wood Scott-B07421; x...@theia.denx.de; u-boot@lists.denx.de; aflem...@gmail.com Subject: Re: [U-Boot] [PATCH] common/Makefile: Add new symbol CONFIG_SPL_ENV_SUPPORT for environment in SPL
On 05/22/2013 01:09:07 AM, Stefan Roese wrote: > (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! Why is it including env_nowhere.o then? When you say "the a3m071 SPL U-Boot version", do you mean the SPL itself, or the entire configuration that happens to include an SPL? [Zhang Ying] The a3m071 SPL has not included env_nowhere.o, it only included env_flash.o and CONFIG_ENV_IS_IN_FLASH is set. The am335x and pcm051 SPL included env_nowhere.o and CONFIG_ENV_IS_NOWHERE is set. Meanwhile CONFIG_SPL_NET_SUPPORT is set. What this meant is CONFIG_SPL_NET_SUPPORT only co-exist with CONFIG_ENV_IS_NOWHERE in the SPL. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
