From naveen.mamindlapalli@gmail.com Fri Jan 22 06:59:06 2010
Received: from mail-pw0-f51.google.com ([209.85.160.51])
	by stoneboat.aleph1.co.uk with esmtp (Exim 4.69)
	(envelope-from <naveen.mamindlapalli@gmail.com>) id 1NYDTx-0003Bo-8S
	for yaffs@lists.aleph1.co.uk; Fri, 22 Jan 2010 06:59:06 +0000
Received: by pwj15 with SMTP id 15so561653pwj.30
	for <yaffs@lists.aleph1.co.uk>; Thu, 21 Jan 2010 22:58:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
	h=domainkey-signature:mime-version:received:in-reply-to:references
	:date:message-id:subject:from:to:content-type;
	bh=t2qvflTUzSo0sTJMoJbYP9Tsc3L8e4RTSeO1Pgt0CTM=;
	b=r+fFslSKz76C62nliZsy7/XcFgGOopbDqunVjztJ/jfMSvurKX2D3R75VJuA2cldsw
	W0UbVmy/Cmk9XMadkMIit54NrL2udrlBBBHD3BYvQSJcfHb+Jbyer2gPe+vTM2F7yhWc
	0hvaQ74swpq48Hqu9RkvX+xUIkX+8zo5sg0jU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	b=Ho3J1FZc63bx4Y+D7O+y1mXr7T6NndD5Ty9RzLdj9BKiEh8xrhNOGRZWuKZrDuI88l
	Z5djEv+c+/T1sYR7eNgg81RNFzoPKz490WJfouvhOulFGgp8zy6xTpwnX3fKMVZICiNg
	3OUViG1oQH71YZrERP4S5DjlEKwT/rBj3rbLQ=
MIME-Version: 1.0
Received: by 10.143.25.22 with SMTP id c22mr1743447wfj.195.1264143534365; Thu, 
	21 Jan 2010 22:58:54 -0800 (PST)
In-Reply-To: <8343c0eb1001212249k1c708f8sef5f6df0aa1c139a@mail.gmail.com>
References: <8343c0eb1001212249k1c708f8sef5f6df0aa1c139a@mail.gmail.com>
Date: Fri, 22 Jan 2010 12:28:54 +0530
Message-ID: <8343c0eb1001212258x7cf584det3e5350f620e55ee@mail.gmail.com>
From: Naveen Mamindlapalli <naveen.mamindlapalli@gmail.com>
To: yaffs@lists.aleph1.co.uk
Content-Type: multipart/alternative; boundary=001636e0b6344f9c20047dbb5a79
X-SA-Exim-Connect-IP: 209.85.160.51
X-SA-Exim-Mail-From: naveen.mamindlapalli@gmail.com
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
	stoneboat.aleph1.co.uk
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=4.5 tests=BAYES_00,HTML_MESSAGE,
	SPF_PASS autolearn=no version=3.2.5
X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000)
X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk)
Subject: [Yaffs] Yaffs bad block management
X-BeenThere: yaffs@lists.aleph1.co.uk
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: Discussion of YAFFS NAND flash filesystem <yaffs.lists.aleph1.co.uk>
List-Unsubscribe: <http://lists.aleph1.co.uk/cgi-bin/mailman/options/yaffs>,
	<mailto:yaffs-request@lists.aleph1.co.uk?subject=unsubscribe>
List-Archive: <http://lists.aleph1.co.uk/lurker/list/yaffs.html>
List-Post: <mailto:yaffs@lists.aleph1.co.uk>
List-Help: <mailto:yaffs-request@lists.aleph1.co.uk?subject=help>
List-Subscribe: <http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs>,
	<mailto:yaffs-request@lists.aleph1.co.uk?subject=subscribe>
X-List-Received-Date: Fri, 22 Jan 2010 06:59:06 -0000

--001636e0b6344f9c20047dbb5a79
Content-Type: text/plain; charset=ISO-8859-1

Hi,

My question is:

How does YAFFS handle bad blocks in NAND flash while programming? When it
encounters a bad block while programming, to which good block it will
program. Is there any online documentation which talks about YAFFS bad block
management.

Thanks

Regards,

--001636e0b6344f9c20047dbb5a79
Content-Type: text/html; charset=ISO-8859-1

Hi, <br><br>My question is:<br><br>How does YAFFS handle bad blocks in NAND flash
while programming? When it encounters a bad block while programming, to
which good block it will program. Is there any online documentation
which talks about YAFFS bad block management.<br>
<br>Thanks<br><br>Regards,
<br>

--001636e0b6344f9c20047dbb5a79--


