From manningc2@actrix.gen.nz Tue May 12 00:51:44 2009 Received: from smtp.firstline.co.nz ([203.167.210.162] helo=firstline.co.nz) by stoneboat.aleph1.co.uk with smtp (Exim 4.69) (envelope-from ) id 1M3fHT-0002mZ-BI for yaffs@lists.aleph1.co.uk; Tue, 12 May 2009 00:51:43 +0100 Received: (qmail 8540 invoked by uid 453); 11 May 2009 23:51:27 -0000 X-Virus-Checked: Checked by ClamAV on firstline.co.nz Received: from Unknown (HELO linux-dual-head.local) (10.14.210.25) by firstline.co.nz (qpsmtpd/0.40) with ESMTP; Tue, 12 May 2009 11:51:27 +1200 From: Charles Manning To: yaffs@lists.aleph1.co.uk Date: Tue, 12 May 2009 11:51:26 +1200 User-Agent: KMail/1.9.10 References: <49F72859.3050104@rsc.bg> <49F95555.4030400@rsc.bg> In-Reply-To: <49F95555.4030400@rsc.bg> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200905121151.27081.manningc2@actrix.gen.nz> X-SA-Exim-Connect-IP: 203.167.210.162 X-SA-Exim-Mail-From: manningc2@actrix.gen.nz 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.0 required=5.0 tests=AWL,BAYES_00,SPF_NEUTRAL 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) Cc: Stanislav Popov Subject: Re: [Yaffs] NAND + YAFFS2 - bad blocks 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: Mon, 11 May 2009 23:51:44 -0000 On Thursday 30 April 2009 19:37:57 Stanislav Popov wrote: > Hi, > > Maybe I found the source of the issue. > I put some delays after evry chunk write in yaffs (my fs in yaffs) and > it's working fine. > So the issue comes from timing configuration... > Where do you think could be the real source of the issue? - driver > configuration? EMIF configuration? Hardware Issue? Good to see you're identified a specific issue. Any of the above. Something else to consider is caching. If your NAND accesses are being cached then that will play merry hell with the signals that get to the NAND chips. Driver and hardware timing are intertwined and it is often not realistic to say that the hardware is good but the driver is faulty, or vice versa. I once fixed a lubrication problem in software... but that's a story for another day! -- CHarles