On 23/05/18 11:53, Lucas Stach wrote: > Hi Tomi, > > Am Mittwoch, den 23.05.2018, 11:40 +0300 schrieb Tomi Valkeinen: >> Hi Lucas, >> >> Julien has written an X driver for OMAP5 SoC (which has Vivante's >> GC320). We're seeing a memory leak when using omapdrm for display and >> etnaviv for X 2D rendering. The X driver uses DRI3, so dmabuf >> import/export is involved. > > Why don't you extend the xf86-video-armada driver? It already supports > a load of Xrender and Compositing acceleration using the GC320. Adding > another scanout device shouldn't be hard. I don't know, I'll let Julien answer to that =). I think he had the armada driver working too. >> With each run, I can see buffers being left lying around, visible in >> both omapdrm's and etnaviv's 'gem' debugfs file. And they're there >> even after killing X. >> >> If I try to rmmod etnaviv, I get the warnings below. Unloading >> omapdrm is not possible, as it's being referenced by something >> (presumably by etnaviv having imported omapdrm's dmabufs). >> >> I haven't debugged this much yet, but we do use dmabuf import & >> export successfully with omapdrm and v4l2. Has etnaviv dmabuf >> import/export been tested? > > Yes, dma-buf import/export with etnaviv is extensively being used, as > we need to work with imx-drm on the scanout side and a V4L2 driven VPU > for video-decode. Ok, thanks. I need to study this further. Tomi -- Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
