From fd69234db004e98c663f5c6c4360d2cecaa8a4df Mon Sep 17 00:00:00 2001 From: Keith Packard Date: Sun, 6 Jun 2010 15:21:28 -0700 Subject: Ignore RandR timestamps harder Checking timestamps in post 1.1 randr requests was never a good idea, let's ignore them and just make the configuration changes. Signed-off-by: Keith Packard Acked-by: Chase Douglas --- randr/rrcrtc.c | 33 --------------------------------- 1 file changed, 33 deletions(-) diff --git a/randr/rrcrtc.c b/randr/rrcrtc.c index f5fe76512..14f6e45ac 100644 --- a/randr/rrcrtc.c +++ b/randr/rrcrtc.c @@ -863,19 +863,6 @@ ProcRRSetCrtcConfig (ClientPtr client) goto sendReply; } -#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 - /* * Validate requested rotation */ @@ -948,16 +935,6 @@ ProcRRSetCrtcConfig (ClientPtr client) #endif } - /* - * Make sure the requested set-time is not older than - * the last set-time - */ - if (CompareTimeStamps (time, pScrPriv->lastSetTime) < 0) - { - rep.status = RRSetConfigInvalidTime; - goto sendReply; - } - if (!RRCrtcSet (crtc, mode, stuff->x, stuff->y, rotation, numOutputs, outputs)) { @@ -1088,16 +1065,6 @@ ProcRRSetPanning (ClientPtr client) time = ClientTimeToServerTime(stuff->timestamp); - /* - * Make sure the requested set-time is not older than - * the last set-time - */ - if (CompareTimeStamps (time, pScrPriv->lastSetTime) < 0) - { - rep.status = RRSetConfigInvalidTime; - goto sendReply; - } - if (!pScrPriv->rrGetPanning) return RRErrorBase + BadRRCrtc; -- cgit v1.2.3