intel: fixup damage posting to be done correctly around slave pixmap

This fixes the damage posting to happen in the correct ordering,
not sure if this fixes anything, but it should make things more consistent.

Signed-off-by: Dave Airlie <airlied@redhat.com>
This commit is contained in:
Dave Airlie 2013-01-07 13:57:21 +10:00
parent 5891c89ff2
commit c789d06cf8
1 changed files with 5 additions and 3 deletions

View File

@ -696,6 +696,7 @@ redisplay_dirty(ScreenPtr screen, PixmapDirtyUpdatePtr dirty)
PixmapRegionInit(&pixregion, dirty->slave_dst->master_pixmap);
DamageRegionAppend(&dirty->slave_dst->drawable, &pixregion);
PixmapSyncDirtyHelper(dirty, &pixregion);
intel_batch_submit(scrn);
if (!intel->has_prime_vmap_flush) {
@ -704,9 +705,10 @@ redisplay_dirty(ScreenPtr screen, PixmapDirtyUpdatePtr dirty)
drm_intel_bo_map(bo, FALSE);
drm_intel_bo_unmap(bo);
xf86UnblockSIGIO(was_blocked);
}
DamageRegionAppend(&dirty->slave_dst->drawable, &pixregion);
RegionUninit(&pixregion);
}
DamageRegionProcessPending(&dirty->slave_dst->drawable);
RegionUninit(&pixregion);
return 0;
}