From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Thu, 24 Jun 2010 10:36:17 -0500
Subject: [U-Boot] handling of bad blocks in nand
In-Reply-To: <AANLkTiktrnXK-erEMjHh9ALHMOhfJZMr09G57fidAsv1@mail.gmail.com>
References: <AANLkTik0ijuWUWHEXdNcWaQGQOloM2tnxlAt11c1dt0j@mail.gmail.com>	<20100623190839.GA6766@schlenkerla.am.freescale.net>
	<AANLkTiktrnXK-erEMjHh9ALHMOhfJZMr09G57fidAsv1@mail.gmail.com>
Message-ID: <4C237B71.1010404@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 06/24/2010 01:28 AM, Arno Steffen wrote:
> does it mean in other words - I don't have to care for the bad block,
> can write on the bad block address as it would be ok?

You can't write directly to that block, but it can be included in a 
range of blocks as long as the range is large enough to hold the data 
blocks plus the bad blocks.

> The only thing I have to care is, that I have leave enough space
> between the partitions. As for instance : I need 10 blocks for a
> certain filesystem, give it 12 ? So it could correct 2 bad blocks in
> this range.

Right.

-Scott