From rogerz.zhang@gmail.com Wed Apr 02 07:33:54 2008
Received: from ti-out-0910.google.com ([209.85.142.188])
	by stoneboat.aleph1.co.uk with esmtp (Exim 4.63)
	(envelope-from <rogerz.zhang@gmail.com>) id 1JgwXZ-0003k2-UW
	for yaffs@lists.aleph1.co.uk; Wed, 02 Apr 2008 07:33:54 +0100
Received: by ti-out-0910.google.com with SMTP id j3so969200tid.20
	for <yaffs@lists.aleph1.co.uk>; Tue, 01 Apr 2008 23:33:43 -0700 (PDT)
Received: by 10.110.68.10 with SMTP id q10mr4118281tia.28.1207118023507;
	Tue, 01 Apr 2008 23:33:43 -0700 (PDT)
Received: by 10.110.2.18 with HTTP; Tue, 1 Apr 2008 23:33:43 -0700 (PDT)
Message-ID: <1a3566520804012333g6c0fdd4es77cb789d8381de6@mail.gmail.com>
Date: Wed, 2 Apr 2008 14:33:43 +0800
From: rogerz <rogerz.zhang@gmail.com>
To: yaffs@lists.aleph1.co.uk
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_3539_24014103.1207118023507"
X-SA-Exim-Connect-IP: 209.85.142.188
X-SA-Exim-Mail-From: rogerz.zhang@gmail.com
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.6 required=5.0 tests=BAYES_00,HTML_MESSAGE,
	SPF_PASS 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: [Yaffs] [YAFFS] How should I implement yflash_MarkNANDBlockBad in
	direct interface?
X-BeenThere: yaffs@lists.aleph1.co.uk
X-Mailman-Version: 2.1.9
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/listinfo/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: Wed, 02 Apr 2008 06:33:54 -0000

------=_Part_3539_24014103.1207118023507
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The sample code in direct folder doesn't implement yflash_MarkNANDBlockBad
fully. does it?

In yaffs_ramem2k.c, nandemu2k_MarkNANDBlockBad simply clear all the content
of a PackedTags2.
nandemul2k_QueryNANDBlock calls nandemul2k_ReadChunkWithTagsFromNAND to read
tags unpacked from PackedTags2
During the unpack procedure, yaffs_UnpackTags always mark a block not bad.

So I don't think yflash_MarkNANDBlockBad can actually mark a block bad. Is
it true?

------=_Part_3539_24014103.1207118023507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

The sample code in direct folder doesn&#39;t implement yflash_MarkNANDBlockBad fully. does it?<br><br>In yaffs_ramem2k.c, nandemu2k_MarkNANDBlockBad simply clear all the content of a PackedTags2.<br>nandemul2k_QueryNANDBlock calls nandemul2k_ReadChunkWithTagsFromNAND to read tags unpacked  from PackedTags2<br>
During the unpack procedure, yaffs_UnpackTags always mark a block not bad. <br><br>So I don&#39;t think yflash_MarkNANDBlockBad can actually mark a block bad. Is it true?<br><br><br>

------=_Part_3539_24014103.1207118023507--