dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Julien Boulnois <jboulnois@gmail.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: omapdrm + etnaviv memory leak
Date: Wed, 23 May 2018 16:16:50 +0200	[thread overview]
Message-ID: <CAB8EWQCJCTUJis-qt7+aMMfYTzD0fThG5i_mTGKE2O3RghXVSA@mail.gmail.com> (raw)
In-Reply-To: <6080b3f2-0fe6-dee7-331e-f2c0a9a3aa9d@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 1256 bytes --]

Hi Lucas,

2018-05-23 14:08 GMT+02:00 Tomi Valkeinen <tomi.valkeinen@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
(Beagleboard X15).

Regards

-- 
Julien Boulnois

[-- Attachment #1.2: Type: text/html, Size: 1862 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-05-23 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  8:40 omapdrm + etnaviv memory leak Tomi Valkeinen
2018-05-23  8:53 ` Lucas Stach
2018-05-23 12:08   ` Tomi Valkeinen
2018-05-23 14:16     ` Julien Boulnois [this message]
2018-05-24  8:39   ` Tomi Valkeinen
2018-05-24  8:43     ` Lucas Stach
2018-05-24 14:04       ` Lucas Stach

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAB8EWQCJCTUJis-qt7+aMMfYTzD0fThG5i_mTGKE2O3RghXVSA@mail.gmail.com \
    --to=jboulnois@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tomi.valkeinen@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).