omapdrm + etnaviv memory leak
jboulnois at gmail.com
Wed May 23 14:16:50 UTC 2018
2018-05-23 14:08 GMT+02:00 Tomi Valkeinen <tomi.valkeinen at ti.com>:
> 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.
First of all, for fun and to educate myself ! Secondly, I found that
xf86-video-armada was pretty complex. I wanted to do something simpler
using existing higher level EXA API. Finally, when we started to work on
that with Tomi two years ago, the armada driver looked unmaintained and I
failed to get the DRI3/present part working. So it was actually easier to
work together using a brand new driver since we share the same hardware
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dri-devel