From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] imx6-sabresd/readme.txt: Improve Qt5 Cinematic Demo instructions
Date: Wed, 9 Oct 2019 13:56:00 -0300 [thread overview]
Message-ID: <20191009165601.3424-3-festevam@gmail.com> (raw)
In-Reply-To: <20191009165601.3424-1-festevam@gmail.com>
QT_QPA_EGLFS_ALWAYS_SET_MODE=1 needs to be exported, otherwise the Qt5
Cinematic demo throws a storm of the following messages:
Could not queue DRM page flip on screen LVDS1 (Invalid argument)
Improve the instructions by mentioning such requirement.
Signed-off-by: Fabio Estevam <festevam@gmail.com>
---
board/freescale/imx6-sabresd/readme.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/board/freescale/imx6-sabresd/readme.txt b/board/freescale/imx6-sabresd/readme.txt
index f09ff5caf4..292dab72c4 100644
--- a/board/freescale/imx6-sabresd/readme.txt
+++ b/board/freescale/imx6-sabresd/readme.txt
@@ -80,6 +80,7 @@ Running kmscube application:
Running Qt5 Cinematic Demo:
# export QT_QPA_EGLFS_KMS_CONFIG=/root/sabresd.json
+# export QT_QPA_EGLFS_ALWAYS_SET_MODE=1
# /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
Running gl2mark benchmark:
--
2.17.1
next prev parent reply other threads:[~2019-10-09 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 16:55 [Buildroot] [PATCH 1/4] configs/imx6-sabresd_qt5: Move mdev from eudev Fabio Estevam
2019-10-09 16:55 ` [Buildroot] [PATCH 2/4] configs/imx6-sabresd_qt5: Select the KMSRO gallium driver Fabio Estevam
2019-10-09 16:56 ` Fabio Estevam [this message]
2019-10-09 16:56 ` [Buildroot] [PATCH 4/4] configs/imx6-sabresd: Bump U-Boot and kernel versions Fabio Estevam
2019-10-09 19:14 ` [Buildroot] [PATCH 1/4] configs/imx6-sabresd_qt5: Move mdev from eudev Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191009165601.3424-3-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox