>
>
> >
> > Current MM:
> > 1. drm_gem_cma_object, only support contiguous memory
>
> Please note that drm_gem_cma_object only looks at memory after the MMU
> has done the mapping. If you have a good IOMMU driver that registers
> correctly the dma_ops then you can allocate memory from anywhere and
On Tue, Feb 13, 2018 at 09:34:26PM +0800, Qiang Yu wrote:
> Hi guys,
>
> I'm working on the Lima project for ARM mali400/450 GPU. Now lima
> kernel driver uses CMA for all buffers, but mali400/450 GPU has MMU
> for each vertex/fragment shader processor, so I want to refine the lima
> kernel driver
>
>
> >
> > My requirement:
> > 1. support non-contiguous memory allocation as GPU buffer
> > 2. support contiguous memory allocation too for exporting to some
> > display DRM driver as framebuffer
>
> btw, I think etnaviv deals w/ contiguous scanout buffer by just
> importing the scanout buffer fr
On Tue, Feb 13, 2018 at 8:34 AM, Qiang Yu wrote:
> Hi guys,
>
> I'm working on the Lima project for ARM mali400/450 GPU. Now lima
> kernel driver uses CMA for all buffers, but mali400/450 GPU has MMU
> for each vertex/fragment shader processor, so I want to refine the lima
> kernel driver for non-
Hi guys,
I'm working on the Lima project for ARM mali400/450 GPU. Now lima
kernel driver uses CMA for all buffers, but mali400/450 GPU has MMU
for each vertex/fragment shader processor, so I want to refine the lima
kernel driver for non-contiguous memory support.
After some investigation on curre
