FUJITA Tomonori wrote:
On Fri, 12 Mar 2010 20:12:39 +0100
Albert Herranz albert_herr...@yahoo.es wrote:
The current SWIOTLB code does not support NOT_COHERENT_CACHE platforms.
This patch adds support for NOT_COHERENT_CACHE platforms to SWIOTLB by
adding two platform specific functions
FUJITA Tomonori wrote:
If we want to make swiotlb generic (make on any architectures), we
need to handle more cache issues here, I think. So it's better to have
more generic ways instead of adding hooks to some archs.
Ok. So what would be an acceptable way of handling this in a generic way?
On Fri, 12 Mar 2010 20:12:39 +0100
Albert Herranz albert_herr...@yahoo.es wrote:
The current SWIOTLB code does not support NOT_COHERENT_CACHE platforms.
This patch adds support for NOT_COHERENT_CACHE platforms to SWIOTLB by
adding two platform specific functions swiotlb_dma_sync_page() and
On Tue, 16 Mar 2010 10:54:40 +0900
FUJITA Tomonori fujita.tomon...@lab.ntt.co.jp wrote:
On Fri, 12 Mar 2010 20:12:39 +0100
Albert Herranz albert_herr...@yahoo.es wrote:
The current SWIOTLB code does not support NOT_COHERENT_CACHE platforms.
This patch adds support for NOT_COHERENT_CACHE
The current SWIOTLB code does not support NOT_COHERENT_CACHE platforms.
This patch adds support for NOT_COHERENT_CACHE platforms to SWIOTLB by
adding two platform specific functions swiotlb_dma_sync_page() and
swiotlb_dma_sync() which can be used to explicitly manage cache coherency.
On PowerPC
