Steve wrote: > These processors will corrupt data if accessing the local bus with > unaligned addresses. This version fixes the typical case of copying from > Flash on the local bus by keeping the source address always aligned.
As Dave said in May of 2008[1], the map driver is advertising xip access to userspace so jffs2 is taking the XIP path and doing straight memcpy. My reading of the mtd code says this is because map_is_linear() is true a cfi cmdset 0001 nor flash will create a point function which jffs2 calls and it finds it will map the whole fs, so it just reads at will from the direct mapping. If the point fails to map the whole device, then jffs2 will use the mtd mapping driver to copy to a buffer, and the default mapping drivers will use memcpy_fromio to fill this buffer. Steve, can you verify this by setting phys to NO_XIP in the mapping driver and setting CONFIG_MTD_COMPLEX_MAPPINGS? This is just a test, as it is aparent this driver needs to have a custom mapping driver that handles the alignment and read/modfiy/write issues -- the existing memcopy_*io assumes byte writes are always ok which is not the case for this processor and bus. [1] http://thread.gmane.org/gmane.linux.drivers.mtd/21521 (found from the link in Albrecht's reply) milton _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
