From s.popov@rsc.bg Tue Apr 28 17:01:25 2009 Received: from sigma.superhosting.bg ([91.196.124.10]) by stoneboat.aleph1.co.uk with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1LypkG-0005FZ-4F for yaffs@lists.aleph1.co.uk; Tue, 28 Apr 2009 17:01:25 +0100 Received: from blueice1n1.de.ibm.com ([195.212.29.163] helo=[9.157.146.18]) by sigma.superhosting.bg with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1Lypk5-0006Ph-U4 for yaffs@lists.aleph1.co.uk; Tue, 28 Apr 2009 19:01:10 +0300 Message-ID: <49F72842.5070307@rsc.bg> Date: Tue, 28 Apr 2009 19:01:06 +0300 From: Stanislav Popov User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: yaffs@lists.aleph1.co.uk Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sigma.superhosting.bg X-AntiAbuse: Original Domain - lists.aleph1.co.uk X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - rsc.bg X-Source: X-Source-Args: X-Source-Dir: X-SA-Exim-Connect-IP: 91.196.124.10 X-SA-Exim-Mail-From: s.popov@rsc.bg 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=5.0 tests=AWL,BAYES_00 autolearn=ham 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] [Fwd: nand oob erase] X-BeenThere: yaffs@lists.aleph1.co.uk X-Mailman-Version: 2.1.11 Precedence: list List-Id: Discussion of YAFFS NAND flash filesystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Apr 2009 16:01:25 -0000 It's ok now! I had to edit the kernel (adding force_erase flag) and there is also a similiar check in flash_eraseall tool ;) Stanislav -------- Original Message -------- Hi, I read fome of your answers in linux forums (http://osdir.com/ml/linux.file-systems.yaffs/2007-04/msg00002.html) I have the same issue but I need to clear the bad block markers in NAND. I don't have nand_scrub in my u-boot so I need to do that it kernel. What should I change and implement in the driver so it will format (erase) the oob? Thanks in advance, Stanislav