Andy Green wrote: > I don't really know why it should not be accepted by MTD_ROM even on > GTA01
Yep, but the NOR is described in the GTA02-specific machine definition. So the GTA01 shouldn't even pick it up. And apparently this is exactly what happens. It's so nice when things work as expected ;-) So the only compatibility issue that remains is when GTA02 devices get upgraded to the new kernel. But then, everyone who has a GTA02 should also have a debug board somewhere _and_ a pretty good idea of what they're doing. > -- I tested it with giving the wrong start address in the platform > stuff on a GTA-02 A4 here and it still had the logical physmap partition > created. Perfect. So all GTA02 will look the same. > On the can't write thing, maybe you might not have the Flash paged in at > all somehow and are getting a hit on MTD_ROM? Normally I see this in dmesg Yeah, with the extended command set, I get reasonable blocks. It's still read-only, though. Gotta check is my hardware combination is actually set up for this. My dmesg output is a little chattier: physmap platform flash device: 00200000 at 18000000 physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0039 Intel/Sharp Extended Query Table at 0x0039 Intel/Sharp Extended Query Table at 0x0039 Intel/Sharp Extended Query Table at 0x0039 Intel/Sharp Extended Query Table at 0x0039 cfi_cmdset_0001: Erase suspend on write enabled erase region 0: offset=0x0,size=0x2000,blocks=8 erase region 1: offset=0x10000,size=0x10000,blocks=31 physmap-flash.0: 1 set(s) of 1 interleaved chips --> 4 partitions of 512 KiB Thanks, - Werner
