Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: Scott Bartolett <SBartolett@thorlabs.com>
Cc: "buildroot@busybox.net" <buildroot@busybox.net>
Subject: Re: [Buildroot] EGLFS Could Not Find DRM Device!
Date: Tue, 17 Aug 2021 20:10:14 +0200	[thread overview]
Message-ID: <20210817201014.235cf403@gmx.net> (raw)
In-Reply-To: <SJ0PR08MB6542DE17A6C96CC4B1B9A6A5B8FE9@SJ0PR08MB6542.namprd08.prod.outlook.com>

Hello Scott,

On Tue, 17 Aug 2021 17:47:49 +0000, Scott Bartolett <SBartolett@thorlabs.com> wrote:

> Hi all,
>
> I'm trying to run a Qt5 application on a Raspberry Pi running buildroot.  The application runs fine when I use the platform plugin linuxfb.  But when I try to use eglfs I'm getting the error that the DRM Device is not found.  I see this error message mentioned often when doing a search, but so far have not found any solution that works for me.  I've selected:
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_V3D
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_VC4
> BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO
> BR2_PACKAGE_MESA3D_OPENGL_ES
> BR2_PACKAGE_QT5BASE_OPENGL_ES2
> BR2_PACKAGE_QT5BASE_EGLFS
>
> Does anyone have any suggestions?

Edit the config.txt file on the first/boot partition on the SD card and
add (for RPi4):

	dtoverlay=vc4-kms-v3d-pi4

or (for Rpi3,...):

	dtoverlay=vc4-kms-v3d

See [1] for details...

Regards,
Peter

[1] https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README

>
> Thanks,
> Scott
>

_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2021-08-17 18:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 17:47 [Buildroot] EGLFS Could Not Find DRM Device! Scott Bartolett
2021-08-17 18:10 ` Peter Seiderer [this message]
2021-08-17 18:59   ` Scott Bartolett
2021-08-18 13:08   ` Scott Bartolett
2021-08-18 16:11     ` Peter Seiderer
     [not found]       ` <SJ0PR08MB6542F033192E0D422DEE4FDDB8FF9@SJ0PR08MB6542.namprd08.prod.outlook.com>
2021-08-18 21:11         ` Peter Seiderer
     [not found]           ` <SJ0PR08MB6542F6819B55EBB098177E0FB8C09@SJ0PR08MB6542.namprd08.prod.outlook.com>
2021-08-19 18:17             ` Peter Seiderer
  -- strict thread matches above, loose matches on Subject: below --
2021-08-29  3:03 Charles Steinkuehler
2021-08-29 15:28 ` Charles Steinkuehler

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=20210817201014.235cf403@gmx.net \
    --to=ps.report@gmx.net \
    --cc=SBartolett@thorlabs.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