From mboxrd@z Thu Jan 1 00:00:00 1970 From: Timur Tabi Date: Tue, 22 May 2007 16:07:07 -0500 Subject: [U-Boot-Users] Question about CFG_ENV_ADDR during RAMBOOT In-Reply-To: <20070522210405.03530353428@atlas.denx.de> References: <20070522210405.03530353428@atlas.denx.de> Message-ID: <46535B7B.2090903@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > In message <46535865.6060400@smiths-aerospace.com> you wrote: >> Looks to me like it would be better defined: >> #define CFG_ENV_SIZE 0x2000 >> #define CFG_ENV_ADDR (CFG_MONITOR_BASE - CFG_ENV_SIZE) > > No, this is broken as CFG_ENV_SIZE may be (and often actually is) > smaller than CFG_ENV_SECT_SIZE Why would that matter? Does the environment need to be located on a sector boundary? > One could argue that a correctly configured ramboot version would > access the original copy of the environment in flash. But such > discussion is void, as ramboot itself it not supported officially. My understanding of ramboot is that its sole purpose is to boot U-Boot when flash isn't working at all, so any ramboot-enabled U-Boot would never access anything on flash. -- Timur Tabi Linux Kernel Developer @ Freescale