From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Mon, 19 Sep 2011 12:54:18 -0500 Subject: [U-Boot] [PATCH 27/31] M28: Save environment in NAND In-Reply-To: <201109171020.04821.marek.vasut@gmail.com> References: <1315514579-19215-1-git-send-email-marek.vasut@gmail.com> <1315514579-19215-28-git-send-email-marek.vasut@gmail.com> <4E73A040.5020202@freescale.com> <201109171020.04821.marek.vasut@gmail.com> Message-ID: <4E7781CA.5030309@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 On 09/17/2011 03:20 AM, Marek Vasut wrote: > On Friday, September 16, 2011 09:15:12 PM Scott Wood wrote: >> Consider using CONFIG_ENV_RANGE to allow for bad blocks. > > How does this actually play with CONFIG_MTDPARTS ? I don't think there's any direct interaction between the environment code and mtdparts. > For you see -- I now have > CONFIG_MTDPARTS "...128k(environment), 128k(redundant-environment)..." > and CONFIG_ENV_SECT_SIZE (128 * 1024). > > So what exactly am I supposed to set into CONFIG_ENV_RANGE and do I have to > modify the CONFIG_MTDPARTS? You'd have to make the environment partitions larger -- the idea is to provide an extra block or two in case of bad blocks. CONFIG_ENV_RANGE would be set to the partition size. -Scott