In linux-2.6.x/drivers/mtd/chips/jedec_probe.c there is a comment
explaining why FF is used to reset the flash, when F0 is the reset
command. Apparently some "misdesigned" Intel chips do not respond to
F0, so many places in the mtd/chips probe code use both F0 and FF.
We've just come across a device, M29W128G from numonyx, which does not
accept the FF command at all (F0 is reset). FF sends the device into
some bizarre state.
How should this be fixed, to be submitted? I'm thinking an option in
mtd/chips/Kconfig to disable the FF hack, and have the option "default
y" to not break legacy systems? should i make this change?
thanks, wilson
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
