On Die, 2011-06-07 at 10:17 +0200, Thomas Hellstrom wrote:
> On 06/06/2011 05:20 PM, James Jones wrote:
> > On 6/6/11 2:09 AM, "Thomas Hellstrom" wrote:
> >
> >
> >> Hi!
> >>
> >> While trying to improve the vmwgfx X driver to better cope with OpenGL
> >> compositors, I noticed that compiz ne
On 06/06/2011 05:20 PM, James Jones wrote:
On 6/6/11 2:09 AM, "Thomas Hellstrom" wrote:
Hi!
While trying to improve the vmwgfx X driver to better cope with OpenGL
compositors, I noticed that compiz never calls glxWaitX() to make sure
the pixmaps that it textures from are updated.
Since w
On 6/6/11 2:09 AM, "Thomas Hellstrom" wrote:
> Hi!
>
> While trying to improve the vmwgfx X driver to better cope with OpenGL
> compositors, I noticed that compiz never calls glxWaitX() to make sure
> the pixmaps that it textures from are updated.
>
> Since we migrate X rendered data to the dri
Hi!
While trying to improve the vmwgfx X driver to better cope with OpenGL
compositors, I noticed that compiz never calls glxWaitX() to make sure
the pixmaps that it textures from are updated.
Since we migrate X rendered data to the dri2 drawables only on demand,
we miss a lot of data.
Goo