From 825b2c2f4a59ac4852f90bbbddf18ab832297fdd Mon Sep 17 00:00:00 2001
From: Matthias Hopf <mhopf@suse.de>
Date: Thu, 4 Dec 2008 16:11:21 +0100
Subject: randr: Nuke config-timestamp for panning

---
 randr/rrcrtc.c | 15 ---------------
 1 file changed, 15 deletions(-)

(limited to 'randr')

diff --git a/randr/rrcrtc.c b/randr/rrcrtc.c
index b8e4d1109..99f7d1ea1 100644
--- a/randr/rrcrtc.c
+++ b/randr/rrcrtc.c
@@ -1056,7 +1056,6 @@ ProcRRSetPanning (ClientPtr client)
     RRCrtcPtr		crtc;
     ScreenPtr		pScreen;
     rrScrPrivPtr	pScrPriv;
-    TimeStamp		configTime;
     TimeStamp		time;
     BoxRec		total;
     BoxRec		tracking;
@@ -1083,21 +1082,7 @@ ProcRRSetPanning (ClientPtr client)
     }
     
     time = ClientTimeToServerTime(stuff->timestamp);
-    configTime = ClientTimeToServerTime(stuff->configTimestamp);
     
-#if 0
-    /*
-     * if the client's config timestamp is not the same as the last config
-     * timestamp, then the config information isn't up-to-date and
-     * can't even be validated
-     */
-    if (CompareTimeStamps (configTime, pScrPriv->lastConfigTime) != 0)
-    {
-	rep.status = RRSetConfigInvalidConfigTime;
-	goto sendReply;
-    }
-#endif
-
     /*
      * Make sure the requested set-time is not older than
      * the last set-time
-- 
cgit v1.2.3