Attachment 88493 Details for Bug 71110 – st/xorg: handle updates to DamageUnregister API

[patch] st/xorg: handle updates to DamageUnregister API

0001-st-xorg-handle-updates-to-DamageUnregister-API.patch (text/plain), 1.41 KB, created by Emil Velikov on 2013-11-01 17:01:37 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Emil Velikov

Created: 2013-11-01 17:01:37 UTC

Size: 1.41 KB

patch

obsolete

>From 3be3b54162e2c95c400870e74dff6028a8387d20 Mon Sep 17 00:00:00 2001
>From: Emil Velikov <emil.l.velikov@gmail.com>
>Date: Fri, 1 Nov 2013 16:44:10 +0000
>Subject: [PATCH] st/xorg: handle updates to DamageUnregister API
>MIME-Version: 1.0
>Content-Type: text/plain; charset=UTF-8
>Content-Transfer-Encoding: 8bit
>
>xserver 1.14.99.2 simplified the DamageUnregister API, by
>dropping the drawable argument.
>Follow xf86-video-intel and xf86-video-vmware approach and
>handle the new API by checking XORG_VERSION_CURRENT.
>
>Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=71110
>Reported-by: MichaÅ GÃ³rny <mgorny@gentoo.org>
>Reported-by: Vinson Lee <vlee@freedesktop.org>
>Signed-off-by: Emil Velikov <emil.l.velikov@gmail.com>
>---
> src/gallium/state_trackers/xorg/xorg_driver.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
>diff --git a/src/gallium/state_trackers/xorg/xorg_driver.c b/src/gallium/state_trackers/xorg/xorg_driver.c
>index 097c354..d252545 100644
>--- a/src/gallium/state_trackers/xorg/xorg_driver.c
>+++ b/src/gallium/state_trackers/xorg/xorg_driver.c
>@@ -1027,7 +1027,11 @@ drv_close_screen(CLOSE_SCREEN_ARGS_DECL)
> 
> #ifdef DRM_MODE_FEATURE_DIRTYFB
>     if (ms->damage) {
>+#if XORG_VERSION_CURRENT >= XORG_VERSION_NUMERIC(1,14,99,2,0)
>+	DamageUnregister(ms->damage);
>+#else
> 	DamageUnregister(&pScreen->GetScreenPixmap(pScreen)->drawable, ms->damage);
>+#endif
> 	DamageDestroy(ms->damage);
> 	ms->damage = NULL;
>     }
>-- 
>1.8.4.2
>

Actions: View | Splinter Review

Attachments on bug 71110: 88493

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.