From d036cdedf0913384b1e45bba80aa2c816be9c350 Mon Sep 17 00:00:00 2001 From: Chris Wilson Date: Sun, 28 Sep 2014 18:00:25 +0100 Subject: [PATCH] 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 --- src/sna/sna_display.c | 5 ++--- 1 file 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 */