summaryrefslogtreecommitdiffstats
path: root/src/gbm/backends
diff options
context:
space:
mode:
authorEric Anholt <[email protected]>2013-06-21 15:34:52 -0700
committerKenneth Graunke <[email protected]>2013-07-31 10:43:35 -0700
commiteed0a80137dfac641adfd39ce316938dbcf2be10 (patch)
tree92b8d389feda3c27a96da2d895a269da52bd50c7 /src/gbm/backends
parentb1ed7202dfb64c01313e78bd4fe290ecd08bf5f7 (diff)
egl: Restore "bogus" DRI2 invalidate event code.
I had removed it in commit 1e7776ca2bc59a6978d9b933d23852d47078dfa8 because it was obviously wrong -- why do we care whether the server is a version that emits events, if we're not watching for the server's events, anyway? And why would you only invalidate on a server that emits invalidate events, when the comment said to emit invalidates if the server *doesn't*? Only, I missed that we otherwise don't flag that our buffers might have changed at swap time at all, so the driver was only checking for new buffers when triggered by the Viewport hack. Of course you don't expect Viewport to be called after a swap. So, this is effectively a revert of the previous commit, except that I dropped the check for only emitting invalidates on a new server -- we *always* need to invalidate if we're doing a SwapBuffers. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=63435 Reviewed-by: Kenneth Graunke <[email protected]> Cc: "9.1 and 9.2" <[email protected]>
Diffstat (limited to 'src/gbm/backends')
0 files changed, 0 insertions, 0 deletions