From jamesk@edmi.com.au Mon May 26 01:13:19 2008 Received: from edmi.com.au ([202.154.109.186]) by stoneboat.aleph1.co.uk with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.63) (envelope-from ) id 1K0QKs-0005nw-Mk for yaffs@lists.aleph1.co.uk; Mon, 26 May 2008 01:13:19 +0100 Received: from edmi.com.au by edmi.com.au (MDaemon PRO v9.6.4) with ESMTP id md50000755707.msg for ; Mon, 26 May 2008 10:12:49 +1000 X-Return-Path: jamesk@edmi.com.au X-Envelope-From: jamesk@edmi.com.au X-MDaemon-Deliver-To: yaffs@lists.aleph1.co.uk X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 26 May 2008 10:12:48 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Yaffs] about retiring block Thread-Index: Aci8ra9BqZ6UnQprSJeEacwDvITr5QCFqzvQ References: From: "James Kehl" To: "hgh" , X-MDAV-Processed: edmi.com.au, Mon, 26 May 2008 10:12:49 +1000 X-SA-Exim-Connect-IP: 202.154.109.186 X-SA-Exim-Mail-From: jamesk@edmi.com.au X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 X-SA-Exim-Version: 4.2.1 (built Tue, 09 Jan 2007 17:23:22 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: Re: [Yaffs] about retiring block X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.9 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2008 00:13:19 -0000 > -----Original Message----- > From: yaffs-bounces@lists.aleph1.co.uk [mailto:yaffs- > bounces@lists.aleph1.co.uk] On Behalf Of hgh > Sent: Friday, 23 May 2008 6:17 PM > To: yaffs@lists.aleph1.co.uk > Subject: [Yaffs] about retiring block >=20 > hi,all > I am a fresher ,just have read the code for a few week. > As I know, the OOB can only be programmed once. But > yaffs_RetireBlock will modify it directly, right? > How that happen? Yaffs1 does do multiple writes to the OOB. This is permissible by single-level flash - you can clear bits at any time, but to set them needs an erase cycle - and Yaffs1 only does that once in the lifetime of the block (to retire it). Yaffs2 does not do multiple writes to the OOB, because it supports multi-level flash (MLC). James