[PATCH 2/4] [RFC] drm/exynos: Mapping of gem objects uses dma_mmap_writecombine

2012-04-16 Thread Inki Dae
sunilm at samsung.com; prathyush.k at samsung.com > Subject: [PATCH 2/4] [RFC] drm/exynos: Mapping of gem objects uses > dma_mmap_writecombine > > GEM objects get mapped to user space in two ways - DIRECT and > INDIRECT mapping. DIRECT mapping is by calling an ioctl and it > maps

RE: [PATCH 2/4] [RFC] drm/exynos: Mapping of gem objects uses dma_mmap_writecombine

2012-04-15 Thread Inki Dae
yus...@samsung.com > Subject: [PATCH 2/4] [RFC] drm/exynos: Mapping of gem objects uses > dma_mmap_writecombine > > GEM objects get mapped to user space in two ways - DIRECT and > INDIRECT mapping. DIRECT mapping is by calling an ioctl and it > maps all the pages to user space by

[PATCH 2/4] [RFC] drm/exynos: Mapping of gem objects uses dma_mmap_writecombine

2012-04-14 Thread Prathyush
GEM objects get mapped to user space in two ways - DIRECT and INDIRECT mapping. DIRECT mapping is by calling an ioctl and it maps all the pages to user space by calling remap-pfn-range. Indirect mapping is done by calling 'mmap'. The actual mapping is done when a page fault gets generated and is ha

[PATCH 2/4] [RFC] drm/exynos: Mapping of gem objects uses dma_mmap_writecombine

2012-04-14 Thread Prathyush
GEM objects get mapped to user space in two ways - DIRECT and INDIRECT mapping. DIRECT mapping is by calling an ioctl and it maps all the pages to user space by calling remap-pfn-range. Indirect mapping is done by calling 'mmap'. The actual mapping is done when a page fault gets generated and is ha