Blame SOURCES/0001-modesetting-Reduce-glamor-initialization-failed-mess.patch

315c3e
From 41e265988a0b6ec456ddd562253e0f82a7c2ede2 Mon Sep 17 00:00:00 2001
315c3e
From: Adam Jackson <ajax@redhat.com>
315c3e
Date: Fri, 27 Sep 2019 11:43:52 -0400
315c3e
Subject: [PATCH xserver] modesetting: Reduce "glamor initialization failed"
315c3e
 message to X_INFO
315c3e
MIME-Version: 1.0
315c3e
Content-Type: text/plain; charset=UTF-8
315c3e
Content-Transfer-Encoding: 8bit
315c3e
315c3e
This might be an error or not, for example refusing to work on llvmpipe
315c3e
is normal and expected. glamor_egl_init() will print X_ERROR messages if
315c3e
appropriate, so we don't need to here.
315c3e
315c3e
Reviewed-by: Michel Dänzer <mdaenzer@redhat.com>
315c3e
315c3e
(cherry picked from commit cbdde938cbaf604741cd057fac743859ada342ec)
315c3e
Signed-off-by: Michel Dänzer <mdaenzer@redhat.com>
315c3e
---
315c3e
 hw/xfree86/drivers/modesetting/driver.c | 2 +-
315c3e
 1 file changed, 1 insertion(+), 1 deletion(-)
315c3e
315c3e
diff --git a/hw/xfree86/drivers/modesetting/driver.c b/hw/xfree86/drivers/modesetting/driver.c
315c3e
index 2aaea5f7d..783d53eaa 100644
315c3e
--- a/hw/xfree86/drivers/modesetting/driver.c
315c3e
+++ b/hw/xfree86/drivers/modesetting/driver.c
315c3e
@@ -772,7 +772,7 @@ try_enable_glamor(ScrnInfoPtr pScrn)
315c3e
             xf86DrvMsg(pScrn->scrnIndex, X_INFO, "glamor initialized\n");
315c3e
             ms->drmmode.glamor = TRUE;
315c3e
         } else {
315c3e
-            xf86DrvMsg(pScrn->scrnIndex, X_ERROR,
315c3e
+            xf86DrvMsg(pScrn->scrnIndex, X_INFO,
315c3e
                        "glamor initialization failed\n");
315c3e
         }
315c3e
     } else {
315c3e
-- 
315c3e
2.26.2
315c3e