On Feb 9, 2007, at 5:10 PM, Timur Tabi wrote:
Kumar Gala wrote:
quoted
It doesn't seem like it's that big of a change. I'd rather the
code clearly do different things for MURAM vs system memory for
ALL accesses.
Why? MURAM acts like RAM, it just needs to be mapped first.
It does from a coherence point of view, but not from an allocation
mechanism.
We should fix it so the driver just has to do dma_alloc_coherent,
dma_free_coherent, and dma_map_*/dma_unmap_*
- k