From: Mike Frysinger Date: Fri, 10 Jul 2009 22:50:56 -0400 Subject: [U-Boot] ENV_IS_EMBEDDED vs CONFIG_ENV_IS_EMBEDDED In-Reply-To: <20090710221726.8AAD9832E416@gemini.denx.de> References: <200906142240.59607.vapier@gentoo.org> <200906190548.37976.vapier@gentoo.org> <20090710221726.8AAD9832E416@gemini.denx.de> Message-ID: <200907102250.57311.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Friday 10 July 2009 18:17:26 Wolfgang Denk wrote: > Mike Frysinger wrote: > > well, is there a downside from moving from ENV_IS_EMBEDDED to > > CONFIG_ENV_IS_EMBEDDED ? we could at least make sure it is kept in sync > > in > > Yes. It's IMHO silly to have to configure something manually (and > keep it in sync with potential changes of some other defines) when it > is as well possible to have that same value computed automatically at > build time. so i should convert ENV_IS_EMBEDDED to CONFIG_ENV_IS_EMBEDDED or i should add to common code logic to force CONFIG_ENV_IS_EMBEDDED when ENV_IS_EMBEDDED is defined by the board ? -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20090710/67e33eb9/attachment.pgp