I found out more about the problem. If I mmap 2 regions that are distinct, even though they map to the same physical address in non-cacheable memory, if I only use one for reading and the other for writing, there is no corruption of linux and the system works. The problem happens when I both read and write to the same mmap'd area.
Easy enough workaround. Now maybe some kernel expert can figure it out??????? Later-- Dave ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
