Intel 28F640 cfi_cmdset_0001 chip is FL_STATUS after MTD_close

David Woodhouse dwmw2 at
Wed Feb 11 10:30:08 EST 2004

On Wed, 2004-02-11 at 15:17 +0000, Cam wrote:
> 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?

> Is there a reason why the chip is not left in the read array state after 
> an MTD_close? My first thought is to modify cfi_intelext_sync, called by 
> MTD_close so that the chip is left in the read array state after the 
> sync command, but being a newcomer to this code I might be missing 
> something important.

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. 


More information about the linux-mtd mailing list