summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2014-09-28 18:00:25 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2014-09-28 18:00:25 +0100
commitd036cdedf0913384b1e45bba80aa2c816be9c350 (patch)
treedad9cd6bbb4a4c5397f24089d835688379e7d1ee
parentac492b9af99919d7c579ee4dd636ef6aab90c945 (diff)
sna: Use move-to-gpu for explicit handling of damage during fbcon copy
Whilst it is unlikely that we do have any damage queued to the frontbuffer prior to the copy, it is safer to use the migration tracking machinery rather than guess. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
-rw-r--r--src/sna/sna_display.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/src/sna/sna_display.c b/src/sna/sna_display.c
index 1407e2b8..999d7b2b 100644
--- a/src/sna/sna_display.c
+++ b/src/sna/sna_display.c
@@ -1624,9 +1624,8 @@ void sna_copy_fbcon(struct sna *sna)
DBG(("%s\n", __FUNCTION__));
assert((sna->flags & SNA_IS_HOSTED) == 0);
- priv = sna_pixmap(sna->front);
- assert(priv);
- if (priv->gpu_bo == NULL)
+ priv = sna_pixmap_move_to_gpu(sna->front, MOVE_WRITE | __MOVE_SCANOUT);
+ if (priv == NULL)
return;
/* Scan the connectors for a framebuffer and assume that is the fbcon */