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>
This commit is contained in:
Thomas Hellstrom
2011-07-09 22:54:41 +02:00
parent eea96a6f5c
commit 858dbcdddb

View File

@@ -271,10 +271,6 @@ dri2_copy_region(DrawablePtr pDraw, RegionPtr pRegion,
RegionPtr myClip;
GCPtr gc;
if (pSrcBuffer->attachment == DRI2BufferFrontLeft &&
pDestBuffer->attachment == DRI2BufferFakeFrontLeft)
LogMessage(X_ERROR, "glxwaitx\n");
/*
* In driCreateBuffers we dewrap windows into the
* backing pixmaps in order to get to the texture.
@@ -332,7 +328,8 @@ dri2_copy_region(DrawablePtr pDraw, RegionPtr pRegion,
* that something changed.
*/
DamageRegionAppend(src_draw, pRegion);
saa_drawable_dirty(src_draw, TRUE, pRegion);
if (pSrcBuffer->attachment != DRI2BufferFrontLeft)
saa_drawable_dirty(src_draw, TRUE, pRegion);
DamageRegionProcessPending(src_draw);
/*