Intel 28F640 cfi_cmdset_0001 chip is FL_STATUS after MTD_close

Cam camilo at
Wed Feb 11 10:44:00 EST 2004


Thanks for the speedy reply,

>>I would have expected the flash to be left in the read array state when 
>>not in use.
> Why? If we've just finished writing to the device, and we're about to
> write to the device again... why change it into read mode?

After the mtd device has been closed, is it not perverse to leave the 
chips unredable? I don't mind if they are showing FL_STATUS while the 
device is busy.

> Mostly if you're going to need this it's because you forgot to wire up
> the RESET line to the flash chips properly, and you're already going to
> die if the user hits the RESET button at the wrong time, or reboots or
> hits SysRq-B, etc. I prefer not to work around this in the generic code,
> since it's actually helpful for some people to realise this problem
> early on. 

It seems as if the linux commands erase and dd behave strangely on my 
board, although what you say about the reset line is also true (I had 
already emailed the board designer).

I have a patch to leave the chip (and driver) in FL_READY state after 
sync, but it sounds like no-one will be interested.


camilo at                                                 <--

More information about the linux-mtd mailing list