CFI Physical Mapped working?
I've been trying to get either the CFI AMD or CFI Physical Mapping to work with no luck. Are there any tricks to making it work? It doesn't look like any of that code is ever called. I can load the modules but nothing ever happens. I've put some printks in the init_module function and nothing ever prints.
I'm running with the code in the 2.4.0test10 tree, I'm going to try the CVS code here shortly though.
Also, what are the differences between the physical mapped interface and CFI? I'm using an AMD 2MB flash, it's the low power one AM29LV160, I believe is the part number. AMD says it's CFI compliant so I'm hoping
it works. I can read it in physical memory as it is now so I know
that it is visible that way, if nothing else. I'm working on a National Semi based product, it has a MediaGX1 and the CS5530A in it if that makes any difference, I'm under the impression that it shouldn't. I'm using their "Centaurus" test board but I have custom "pizza boards" too, the Centaurus is a bit tricky as it has a 256K flash, a 2MB flash and a 5 or 8 MB DoC and there is a chip select that determines which one you're running, if that makes any difference.
thanks,
Ian
To unsubscribe, send "unsubscribe mtd" to [email protected]
Quoted 5 lines · [email protected] said:
I've been trying to get either the CFI AMD or CFI Physical Mapping to work with no luck. Are there any tricks to making it work? It doesn't look like any of that code is ever called. I can load the modules but nothing ever happens. I've put some printks in the
init_modulefunction and nothing ever prints.
There's no known reason why it shouldn't work.
init_physmap() ought to autoload the cfi_probe module, which in turn will autoload the cfi_cmdset_0002 module if it finds an appropriate chip.
You may find it's best to write a custom map driver instead of the physmap driver, which handles the chip select line for you.
--
dwmw2
To unsubscribe, send "unsubscribe mtd" to [email protected]