[PATCH] ARM: kirkwood: Increase NAND chip-delay for DNS-320
andrew at lunn.ch
Sun Oct 28 16:59:56 EDT 2012
On Sun, Oct 28, 2012 at 08:47:42PM +0000, Jamie Lentin wrote:
> The default chip-delay of 25ns is a bit too tight for some DNS-320's,
> increase to 35ns.
> Signed-off-by: Jamie Lentin <jm at lentin.co.uk>
> I now own 2 DNS-320's, the first of which is happy with a mainline
> kernel, the second fills the console with "Bad eraseblock xxx at
> 0x00000xxxxxxx" for every eraseblock and refuses to access the NAND.
> Beyond this they appear identical, and report the same NAND chip
> (I haven't physically checked that it's the same, however).
> The patch below fixes it, however:-
> * Is there something else I should be trying, rather than potentially
> masking the problem?
> * Is chip-delay too low for kirkwood generally?
Do you know what NAND chip it is? We can check the datasheet and see
what is specified.
All kirkwood's use 25ns and i don't think there have been any problems
reported. But that does not mean Dlink have mounted a slower device.
More information about the linux-arm-kernel