2nd CFI chip detection fails sometimes

[Stephane Laroche]

I vote for the 2nd solution, as it's much easier and simpler than the 1st
one.

Also, I don't know how other people use MTD, but in my case I need to write
map drivers for the flash (and specify it's CFI compliant), which implies
that I know it's not RAM...

-Stephane

-----Original Message-----
From: owner-mtd at infradead.org [mailto:owner-mtd at infradead.org]On Behalf
Of David Woodhouse
Sent: Monday, August 07, 2000 10:34
To: David Vrabel
Cc: mtd at infradead.org
Subject: Re: 2nd CFI chip detection fails sometimes



dvrabel at arcom.co.uk said:
>  The line marked error causes problems because it can put the flash
> chip into an error state preventing correct detection.  We need some
> way of knowing if it's RAM before we do the write.  Suggestions
> welcome!

We should probably only put back the original value if we completely fail
to probe the device, _AND_ if it appears to be behaving like RAM (i.e. if
the contents of the address are exactly what we wrote to it.

Alternatively, we could accept the fact that we overwrite some bytes in a
RAM chip when we unload and reload its driver, and just not bother to write
back those bytes at all.

--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org



To unsubscribe, send "unsubscribe mtd" to majordomo at infradead.org