[Bug 16687] Desktop corruption when enabling Desktop Effects

2008-07-12 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=16687 --- Comment #2 from Chris Rankin <[EMAIL PROTECTED]> 2008-07-12 14:28:06 PST --- (In reply to comment #1) > This is a known issue with DRI and compositing at the same time. That might explain the glxgears problem, but there is still the corr

[Bug 16687] Desktop corruption when enabling Desktop Effects

2008-07-12 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=16687 --- Comment #1 from Adam K Kirchhoff <[EMAIL PROTECTED]> 2008-07-12 14:14:16 PST --- This is a known issue with DRI and compositing at the same time. DRI2 resolves this problem, but the radeon driver still has to be updated to it. See http

[Bug 16687] New: Desktop corruption when enabling Desktop Effects

2008-07-12 Thread bugzilla-daemon
http://bugs.freedesktop.org/show_bug.cgi?id=16687 Summary: Desktop corruption when enabling Desktop Effects Product: Mesa Version: CVS Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Prior

Re: Status of everything?

2008-07-12 Thread Johannes Engel
Ben Gamari wrote: > What trees are you pulling from. Pulling from drm/modesetting-gem and > mesa/drm-gem I'm getting some pretty obvious build errors (e.g. struct > drm_gem_open never defined). That's exactly what I am doing. Upto now I did not experience any of these errors. Cheers, Johannes --

Re: cursor handling and updates inside DRM

2008-07-12 Thread Simon Thum
Jesse Barnes wrote: > Right, and it's actually fairly common in other OSes. It sounds like the > biggest chunk of additional code will be dealing with acceleration; I'm not > sure how complex the latest algorithms are... Also input transformation is > an unknown, but it's a bit dubious anyway.

Re: cursor handling and updates inside DRM

2008-07-12 Thread Simon Thum
Tiago Vignatti wrote: > [0] https://bugs.freedesktop.org/attachment.cgi?id=17545 > This doc says that it improves the heavy-load behavior, but I'm > failing to see it. Can you be more specific? Sure. The old code would assume mouse delta = speed. Of course, this assumption is valid only as lo