From: David Brownell Date: Mon, 5 Oct 2009 16:24:28 -0700 Subject: [U-Boot] [patch] dm355evm NAND support In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D9306B45A@dlee01.ent.ti.com> References: <200910042032.49965.david-b@pacbell.net> <200910051338.19595.david-b@pacbell.net> <0554BEF07D437848AF01B9C9B5F0BC5D9306B45A@dlee01.ent.ti.com> Message-ID: <200910051624.28961.david-b@pacbell.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Monday 05 October 2009, Paulraj, Sandeep wrote: > > > I guess that happened after I prepared the patch but before I sent > > it in. ?I'll look; there were some differences still. ?Notably to > > store the environment in the otherwise-unused block zero, > > That is because most users who have used existing TI binaries have > the env stored at 0x3c0000. So if the update the U-Boot binary, they > will still get all their env back. > IIRC this was a customer requirement of ours. I don't follow. Those existing binaries also used the deprecated "infix" OOB scheme, right? The one which trashes the manufacturer bad block markers, and is not compatible with what U-Boot and Linux have agreed to use. Which means that block becomes unreadable anyway. There's no point in trying to preserve it... - Dave