Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] QT 5.6 app with eglfs and etnaviv (imx6 solo, buildroot 2018.02.5)
Date: Fri, 8 Mar 2019 23:52:23 +0100	[thread overview]
Message-ID: <20190308235223.62e76a71@gmx.net> (raw)
In-Reply-To: <CAE58QoMfF2Kwi0Hc_yOeOinoLA-82OfzzeymOBXsjMK=nYoK5g@mail.gmail.com>

Hello Juan,

On Thu, 7 Mar 2019 23:00:19 +0000, "Juan A. Rubio" <jarubio2001@gmail.com> wrote:

> Hello,
> 
> I'm trying to get my Qt 5.6 app to run with the etnaviv driver instead
> of vivante. My app has so far been running without any problems with
> the vivante driver (I'm using NXP's 4.9.11 kernel). So now I would
> like to try and see if I can switch to the community driver and mesa.
> 
> These are the variables that I've been exporting with the vivante driver:
> FB_MULTI_BUFFER=3
> QT_QPA_EGLFS_INTEGRATION=eglfs_viv
> 
> For etnaviv, I'm doing:
> QT_QPA_EGLFS_INTEGRATION=eglfs_kms
> 
> But I'm getting this error::
> gbm: failed to open any driver (search paths /usr/lib/dri)
> gbm: Last dlopen error: /usr/lib/dri/vivante_dri.so: cannot open
> shared object file: No such file or directory
> failed to load driver: vivante
> 
> These are the contents of /usr/lib/dri/
> # ls /usr/lib/dri/
> etnaviv_dri.so     imx-drm_dri.so     kms_swrast_dri.so  swrast_dri.so
> 
> And I'm enabling these packages:
> BR2_PACKAGE_MESA3D=y
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER=y
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_ETNAVIV=y
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SWRAST=y
> BR2_PACKAGE_MESA3D_DRI_DRIVER=y
> BR2_PACKAGE_MESA3D_OPENGL_ES=y
> BR2_PACKAGE_MESA3D_OPENGL_EGL=y
> BR2_PACKAGE_MESA3D_OPENGL_TEXTURE_FLOAT=y
> 
> BR2_PACKAGE_LIBDRM=y
> BR2_PACKAGE_LIBDRM_HAS_ATOMIC=y
> BR2_PACKAGE_LIBDRM_ENABLE_ATOMIC=y
> BR2_PACKAGE_LIBDRM_ETNAVIV=y
> BR2_PACKAGE_KMSXX=y
> 
> I'm obviously missing something here. Any help would be very much appreciated.

Mind to share your complete .config/defconfig?

Did your run an complete re-build (make clean; make), see [1]?

Regards,
Peter

[1] https://buildroot.org/downloads/manual/manual.html#full-rebuild

> 
> Thanks,
> Juan
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2019-03-08 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 23:00 [Buildroot] QT 5.6 app with eglfs and etnaviv (imx6 solo, buildroot 2018.02.5) Juan A. Rubio
2019-03-08 22:52 ` Peter Seiderer [this message]
2019-03-08 23:04   ` Fabio Estevam
2019-03-08 23:42     ` Juan A. Rubio
2019-03-09 14:06       ` Fabio Estevam

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=20190308235223.62e76a71@gmx.net \
    --to=ps.report@gmx.net \
    --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