Issue with DEBUG_LOCK_BITS

[David Woodhouse]

On Mon, 2004-03-22 at 17:07 -0600, Eisenhut, Daniel (MED) wrote:
> In cfi_intelext_lock() and cfi_intelext_unlock()... if you have enabled
> DEBUG_LOCK_BITS, do_printlockstatus_oneblock is called which sends the
> command 0xff before returning.  This places the chip in Read Array mode.
> Then do_xxlock_oneblock calls get_chip.  If the chip->state equals
> FL_STATUS, it attempts to read the status register.  This naturally fails
> since it is in Read Array mode, not Read Status mode.

Thanks for the report.

But now you leave it in JEDEC Query mode, not Read Status mode. Surely
the correct fix is to just set chip->state appropriately to reflect what
you've just done to the chip?

Can you test what I just committed to CVS, please?

-- 
dwmw2