Author: Jonathan McDowell Date: To: balloon Subject: Re: [Balloon] Bad blocks caused by expiring mtd status poll loop in
2.6.29-rc7
On Thu, Mar 26, 2009 at 10:31:35PM +0000, Chris Jones wrote:
> - are we currently trying to run NAND bus cycles too fast? This is
> moderately unlikely since we slowed it down hugely to make the minipug
> LCDs work over Samosa, unless Jim was running an old bootldr.
As Jim has said, he wasn't running the new bootldr, so it's quite
possible that would have sorted things out.
> - do we want to observe NAND_RNB in hardware (thus locking up the bus
> while the NAND gets its act together) or in software? I'm not even
> sure that this is an appropriate question to ask, but someone else may
> have a quick answer before I go and grub around in data sheets and
> kernel source.
Hooking up support for a NAND ready line in the kernel mtd driver is
easy; I hadn't realised we weren't already doing that. I can't actually
see where NAND_RNB gets mapped to for reading though?
(text/plain)