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: Wed, 18 Aug 2021 23:11:10 +0200 [thread overview]
Message-ID: <20210818231110.390d9064@gmx.net> (raw)
In-Reply-To: <SJ0PR08MB6542F033192E0D422DEE4FDDB8FF9@SJ0PR08MB6542.namprd08.prod.outlook.com>
Hello Scott,
On Wed, 18 Aug 2021 20:28:12 +0000, Scott Bartolett <SBartolett@thorlabs.com> wrote:
> Yes I have the BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS enabled and rpi-firmware/overlays entry in genimage. If I search the buildroot output folder I find this:
>
> ./output/images/rpi-firmware/overlays/vc4-kms-v3d.dtbo
> ./output/images/rpi-firmware/overlays/vc4-kms-v3d-pi4.dtbo
> ./output/build/rpi-firmware-1a46874494146f470d7a61b0b6f4f15a07dd8b35/boot/overlays/vc4-kms-v3d.dtbo
> ./output/build/rpi-firmware-1a46874494146f470d7a61b0b6f4f15a07dd8b35/boot/overlays/vc4-kms-v3d-pi4.dtbo
>
> But I do not find those files anywhere on the target machine. I am using a root file system overlay. Might that be my problem?
The overlays are stored in the first/boot partition (vfat one where the dtb files,
config.txt and cmdline.txt, bootcode.bin and start.elf and fixup.dat and zimage
are found) and not on the second/root (ext4 one with the complte root file system)
partition of the SD card...
Regards,
Peter
>
> I appreciate your help with this.
>
> Scott
>
>
> -----Original Message-----
> From: Peter Seiderer [mailto:ps.report@gmx.net]
> Sent: Wednesday, August 18, 2021 12:11 PM
> To: Scott Bartolett <SBartolett@thorlabs.com>
> Cc: buildroot@busybox.net
> Subject: Re: [Buildroot] EGLFS Could Not Find DRM Device!
>
> Hello Scott,
>
> On Wed, 18 Aug 2021 13:08:28 +0000, Scott Bartolett <SBartolett@thorlabs.com> wrote:
>
> > Hi Peter,
> >
> > On a raspbian install I find the file vc4-kms-v3d.dtbo. However on the buildroot install, I do not find any files that match vc4-kms-v3d*. I've searched for and enabled additional items in the buildroot config that might be related, but nothing has helped yet.
>
> The buildroot config option is name BR2_PACKAGE_RPI_FIRMWARE_INSTALL_DTB_OVERLAYS,
> do not forget to do a full re-build of the rpi-firmware package after enabling...
>
> For inclusion of the overlay files to the target/SD-card boot/first partition check/add the 'rpi-firmware/overlays' entry in the genimage file (see e.g.
> board/raspberrypi3/genimage-raspberrypi3.cfg for an example)...
>
> Regards,
> Peter
>
> >
> > Thanks,
> > Scott
> >
> >
> > -----Original Message-----
> > From: Peter Seiderer [mailto:ps.report@gmx.net]
> > Sent: Tuesday, August 17, 2021 2:10 PM
> > To: Scott Bartolett <SBartolett@thorlabs.com>
> > Cc: buildroot@busybox.net
> > Subject: Re: [Buildroot] EGLFS Could Not Find DRM Device!
> >
> > 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://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> > ub.com%2Fraspberrypi%2Ffirmware%2Fblob%2Fmaster%2Fboot%2Foverlays%2FRE
> > ADME&data=04%7C01%7CSBartolett%40thorlabs.com%7C2be70acef94f4fd7a6
> > 6e08d96262d8bf%7C411510044224448aa787d4279c1f087d%7C0%7C0%7C6376489989
> > 66807962%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TRayRYYU6JoOopJfA9zspOI
> > n%2FGObRgfP2zYF2bS%2BCEA%3D&reserved=0
> >
> > >
> > > Thanks,
> > > Scott
> > >
> >
>
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-08-18 21:11 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
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 [this message]
[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=20210818231110.390d9064@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