All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] QT5.8 buid failure on master
Date: Sun, 12 Mar 2017 19:43:04 -0300	[thread overview]
Message-ID: <CAOMZO5BdAeVjxVEXcDq5rWS=4XhqF1qJ_hZQA9e3H_NFG+mAJQ@mail.gmail.com> (raw)
In-Reply-To: <CAAMH-ytGnurAFt=BcfK53qJ8OR09o8LAZK2UdCH7nO-1Q=2aQg@mail.gmail.com>

Hi Gary,

On Wed, Mar 8, 2017 at 7:45 AM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:

> However, I've made a discovery regarding the DRI configuration (to
> avoid hardcoding the device). It is actually documented well on Qt
> website:
> http://doc.qt.io/qt-5/embedded-linux.html#eglfs-with-eglfs-kms-backend
> "The KMS/DRM backend also supports custom configurations via a JSON
> file. Set the environment variable QT_QPA_EGLFS_KMS_CONFIG to the name
> of the file to enable this."

Thanks, this did the trick!

Now I can succesfully lauch the Cinematic demo using Buildroot master.
Thanks to Peter for his two Qt5.8 fixes!

Any suggestions for a proper fix on the 'black screen' problem?

Thanks

      parent reply	other threads:[~2017-03-12 22:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 22:41 [Buildroot] QT5.8 buid failure on master Fabio Estevam
2017-03-07  7:33 ` Peter Seiderer
2017-03-07 11:48   ` Gary Bisson
2017-03-07 12:15     ` Jagan Teki
2017-03-07 14:04     ` Peter Seiderer
2017-03-07 16:15       ` Jagan Teki
2017-03-07 16:32         ` Jagan Teki
2017-03-07 16:57         ` Fabio Estevam
2017-03-07 17:11           ` Jagan Teki
2017-03-07 17:16             ` Fabio Estevam
2017-03-07 17:19               ` Jagan Teki
2017-03-07 19:29           ` Peter Seiderer
2017-03-08 10:45             ` Gary Bisson
2017-03-08 11:00               ` Jagan Teki
2017-03-08 11:28                 ` Gary Bisson
2017-03-08 12:19                   ` Jagan Teki
2017-03-12 22:43               ` Fabio Estevam [this message]

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='CAOMZO5BdAeVjxVEXcDq5rWS=4XhqF1qJ_hZQA9e3H_NFG+mAJQ@mail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.