Chris Pringle wrote: > Ah right - that would explain what we're seeing then... Doh. Thought I > might have been onto something then. Is there any way to force a cache > flush? That'd at least prove it was a caching issue if it resolved the > problem. You could enable CONFIG_NOT_COHERENT_CACHE. -Scott