[U-Boot] [PATCH v3] NAND: environment offset in OOB (CONFIG_ENV_OFFSET_OOB)

[Wolfgang Denk]

Dear Ben Gardiner,

In message <1277933528-8335-1-git-send-email-bengardiner at nanometrics.ca> you wrote:
> This is a re-submission of the patch by Harald Welte
> <laforge at openmoko.org> with minor modifications for rebase and changes
> as suggested by Scott Wood <scottwood at freescale.com> [1] [2].
> 
> This patch enables the environment partition to have a run-time dynamic 
> location (offset) in the NAND flash.  The reason for this is simply that 
> all NAND flashes have factory-default bad blocks, and a fixed compile 
> time offset would mean that sometimes the environment partition would 
> live inside factory bad blocks. Since the number of factory default 
> blocks can be quite high (easily 1.3MBytes in current standard 
> components), it is not economic to keep that many spare blocks inside 
> the environment partition.
> 
> With this patch and CONFIG_ENV_OFFSET_OOB enabled, the location of the
> environment partition is stored in the out-of-band (OOB) data of the
> first block in flash. Since the first block is where most systems boot
> from, the vendors guarantee that the first block is not a factory
> default block.

Does this work with redundant environment in NAND?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
One of the advantages of being a captain is being able to ask for ad-
vice without necessarily having to take it.
	-- Kirk, "Dagger of the Mind", stardate 2715.2