Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Requirements for QML in RPi4
Date: Mon, 27 Jan 2020 16:41:25 +0100	[thread overview]
Message-ID: <20200127164125.1ec2b7ff@gmx.net> (raw)
In-Reply-To: <CAPmASevs=kKKCspFM0M_ydbeSzNJLGEEiGmrgb6Ap-RqUtE-Ag@mail.gmail.com>

Hello Andrea,

On Mon, 27 Jan 2020 16:01:17 +0100, Andrea Simeoni <andreasimeoni73@gmail.com> wrote:

> After several years I'm going to give another try to Buildroot :-)
> This time I built an environment for RPi4+Qt5.
> Surely I missed some packages because if I try to run a QML application I
> got the following error:
>
> > Could not find DRM device!
> > Aborted
>
> Instead a Qt5 console application seems to run fine.
>
> I attach my .config file. Hope you can give me some hints!

You seem to have a RPi4-64bit config, trying to run
mesa vc4?

Sorry, not owning an RPi4 for testing, but for the RPi3 you
need to enable the right Device-Tree-Overlay in your config.txt,
e.g. (see the following two links for earlier discussion [1], [2]):

dtoverlay=vc4-fkms-v3d

This may or may not work as RPi3 is VC4 and RPi4 is VC6 ([3]),
but Gentoo claims to have RPi4 running with mesa ([4], [5])...

Alternatively your can try RPi4-32bit and enable rpi-userland/BR2_PACKAGE_RPI_USERLAND
instead of mesa...

Regards,
Peter


[1] http://lists.busybox.net/pipermail/buildroot/2019-October/264561.html
[2] http://lists.busybox.net/pipermail/buildroot/2019-November/265133.html
[3] http://lists.busybox.net/pipermail/buildroot/2019-November/265139.html
[4] http://lists.busybox.net/pipermail/buildroot/2019-November/265153.html
[5] https://github.com/sakaki-/gentoo-on-rpi-64bit


> Best regards
> Andrea

  reply	other threads:[~2020-01-27 15:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 15:01 [Buildroot] Requirements for QML in RPi4 Andrea Simeoni
2020-01-27 15:41 ` Peter Seiderer [this message]
     [not found]   ` <CAPmASevGW-0BY78ETy=p+c3p_cOnWG0DO3d8FV=+U6ij9DynpQ@mail.gmail.com>
2020-01-28  7:29     ` Peter Seiderer
     [not found]     ` <CAPmASetzc-+RCHJT5sqM4QjO-bDfbTuAsJizB26f-5=skjJFbA@mail.gmail.com>
2020-01-28  7:38       ` Peter Seiderer
2020-02-04 14:57         ` Peter Seiderer
2020-02-06 16:54           ` Andrea Simeoni

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=20200127164125.1ec2b7ff@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