vmwgfx: Don't dirty the front buffer as hw when doing a dri2copyregion from it
authorThomas Hellstrom <thellstrom@vmware.com>
Sat, 9 Jul 2011 20:54:41 +0000 (22:54 +0200)
committerThomas Hellstrom <thellstrom@vmware.com>
Sat, 9 Jul 2011 20:59:41 +0000 (22:59 +0200)
commit858dbcdddb35b690a543a103d43dcaeb040260c1
tree8851c64d4c2dc979b9b7ea89d0d74ec2c33a3102
parenteea96a6f5ccc6a3a1e2bb2737f211076de443462
vmwgfx: Don't dirty the front buffer as hw when doing a dri2copyregion from it

When copying from a dri2 buffer we usually dirty it as hw, since dri has
been rendering to it, and there can only be hw contents in the buffer.

However for the real front, X has already done the dirty work for us.

Also remove a glxWaitX() debug message.

This should fix piglit read-front.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
vmwgfx/vmwgfx_dri2.c