Searched hist:e6be133b68ae2c8f89d46da25ed7b31b84793e7e (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/drivers/mtd/chips/ |
| H A D | fwh_lock.h | diff e6be133b68ae2c8f89d46da25ed7b31b84793e7e Wed Mar 28 17:56:28 CDT 2007 Shashi Rao <shashi@sun.com> [MTD] Fix fwh_lock locking
This is on a custom board with a mapping driver access to an ST
M50LPW080 chip. This chip is probed successfully with
do_map_probe("jedec_probe",...). If I use the mtdchar interface to
perform unlock->erase->program->lock on any of the 16 eraseblocks in the
chip, the chip is left in FL_STATUS mode while the data structures
believe that the chip is in FL_READY mode. Hence, any subsequent reads
to any flash byte results in 0x80 being read.
Signed-off-by: Shashi Rao <shashi@sun.com>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
|