intel-virtual-output: Workaround mutter always using the same timestamp
authorChris Wilson <chris@chris-wilson.co.uk>
Wed, 27 Nov 2013 12:57:09 +0000 (12:57 +0000)
committerChris Wilson <chris@chris-wilson.co.uk>
Wed, 27 Nov 2013 12:57:09 +0000 (12:57 +0000)
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
tools/virtual.c

index dd938a0..e522264 100644 (file)
@@ -931,7 +931,8 @@ static int context_update(struct context *ctx)
                return 0;
 
        DBG(("%s timestamp %ld (last %ld)\n", DisplayString(dpy), res->timestamp, ctx->display->timestamp));
-       if (res->timestamp == ctx->display->timestamp) {
+       if (res->timestamp == ctx->display->timestamp &&
+           res->timestamp != res->configTimestamp) { /* mutter be damned */
                XRRFreeScreenResources(res);
                return 0;
        }