Summary: | Regression: i965: severe flicker if window is made fullscreen after xrandr | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Nick Bowler <nbowler> | ||||
Component: | DRM/Intel | Assignee: | Jesse Barnes <jbarnes> | ||||
Status: | CLOSED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | medium | Keywords: | NEEDINFO | ||||
Version: | unspecified | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Nick Bowler
2010-06-02 18:55:13 UTC
Does this still happen with current bits? Several fixes landed in xf86-video-intel, xserver, mesa and libdrm and the kernel that may have affected this. Nevermind, I see it does still happen, debugging now. Created attachment 36695 [details] [review] update dri2 buffers if drawable serial changes Can you give this patch a try? It works for me and I think it's a good way of solving this problem. Yes, that seems to fix it, thanks. This should also fix the cause of: commit e2615cdeef078dbd2e834b68c437f098a92b941d Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Sat May 29 16:37:12 2010 +0100 dri: Only flip if the front and back pixmaps match. An unredirected window (thanks Michel for the reminder) is backed by the Screen pixmap, and so uses a reference of that as its front buffer. The back buffer is a pixmap appropriately sized for the drawable. When the application requests to swap its buffers, obviously we cannot simply exchange the front and back buffer as they do not match, but need to copy the appropriate region from the back to the front. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> (but not eliminate its necessity.) Final fix sent out to the xorg-devel list with keithp's review. Should land in xserver master soon. http://lists.x.org/archives/xorg-devel/2010-July/011048.html http://lists.x.org/archives/xorg-devel/2010-July/011049.html |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.