[Buildroot] EGLFS Could Not Find DRM Device!

[Buildroot] EGLFS Could Not Find DRM Device!

[Scott Bartolett]

[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]

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?

Thanks,
Scott


[-- Attachment #1.2: Type: text/html, Size: 2857 bytes --]

[-- Attachment #2: Type: text/plain, Size: 145 bytes --]

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Peter Seiderer]

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Scott Bartolett]

Hi Peter,

Thanks for getting back to me so quickly.  Unfortunately I had already tried adding that to the config.txt file but still get the same result.

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%2Fgithub.com%2Fraspberrypi%2Ffirmware%2Fblob%2Fmaster%2Fboot%2Foverlays%2FREADME&amp;data=04%7C01%7CSBartolett%40thorlabs.com%7C919da371d81c4cb2c6b308d961aa4771%7C411510044224448aa787d4279c1f087d%7C0%7C0%7C637648206254285944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=QZiffVLIgJEx40pM6%2BtT7y9teGDYDYaqrl8T%2Fz861rM%3D&amp;reserved=0

>
> Thanks,
> Scott
>

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Scott Bartolett]

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.

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%2Fgithub.com%2Fraspberrypi%2Ffirmware%2Fblob%2Fmaster%2Fboot%2Foverlays%2FREADME&amp;data=04%7C01%7CSBartolett%40thorlabs.com%7C919da371d81c4cb2c6b308d961aa4771%7C411510044224448aa787d4279c1f087d%7C0%7C0%7C637648206254285944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=QZiffVLIgJEx40pM6%2BtT7y9teGDYDYaqrl8T%2Fz861rM%3D&amp;reserved=0

>
> Thanks,
> Scott
>

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Peter Seiderer]

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%2Fgithub.com%2Fraspberrypi%2Ffirmware%2Fblob%2Fmaster%2Fboot%2Foverlays%2FREADME&amp;data=04%7C01%7CSBartolett%40thorlabs.com%7C919da371d81c4cb2c6b308d961aa4771%7C411510044224448aa787d4279c1f087d%7C0%7C0%7C637648206254285944%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=QZiffVLIgJEx40pM6%2BtT7y9teGDYDYaqrl8T%2Fz861rM%3D&amp;reserved=0
>
> >
> > Thanks,
> > Scott
> >
>

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Peter Seiderer]

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&amp;data=04%7C01%7CSBartolett%40thorlabs.com%7C2be70acef94f4fd7a6
> > 6e08d96262d8bf%7C411510044224448aa787d4279c1f087d%7C0%7C0%7C6376489989
> > 66807962%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=TRayRYYU6JoOopJfA9zspOI
> > n%2FGObRgfP2zYF2bS%2BCEA%3D&amp;reserved=0
> >
> > >
> > > Thanks,
> > > Scott
> > >
> >
>

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Peter Seiderer]

Hello Scott,

On Thu, 19 Aug 2021 17:32:33 +0000, Scott Bartolett <SBartolett@thorlabs.com> wrote:

> Of course.  I should have realized that.
>
> Hope this doesn't turn out to be a stupid question also, but I just tried to run dtoverlay from the command prompt and it says command not found.  Searched for it on the target machine and did not find it.  Searched for it in the buildroot output folder and found this:
> ./output/build/rpi-firmware-1a46874494146f470d7a61b0b6f4f15a07dd8b35/hardfp/opt/vc/bin/dtoverlay
> ./output/build/rpi-firmware-1a46874494146f470d7a61b0b6f4f15a07dd8b35/opt/vc/bin/dtoverlay

Do not know about a dtoverlay command, the dtoverlay I know is a RPi bootloader
feature controlled by the config.txt file on the first/boot partition of
the SD card, once again:

> > > 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

Regards,
Peter


>
> I just tried the same using the default raspberrypi3_defconfig and get the same result.  Any idea why this would be the case?  I am assuming now that without dtoverlay, vc4-kms-v3d.dtbo is not loading and that is the cause of the DRM Device not found.
>
> We are trying to support a feature that requires rotating our GUI.  This is why we are trying to use the plugin eglfs which supports the rotate=X option.  LinuxFB does not appear to support this.  If I cannot get this to work today, we are going to abandon this feature for now.
>
>
> -----Original Message-----
> From: Peter Seiderer [mailto:ps.report@gmx.net]
> Sent: Wednesday, August 18, 2021 5: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 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/b
> > oot/overlays/vc4-kms-v3d.dtbo
> > ./output/build/rpi-firmware-1a46874494146f470d7a61b0b6f4f15a07dd8b35/b
> > oot/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%2Fgi
> > > th
> > > ub.com%2Fraspberrypi%2Ffirmware%2Fblob%2Fmaster%2Fboot%2Foverlays%2F
> > > RE
> > > ADME&amp;data=04%7C01%7CSBartolett%40thorlabs.com%7C2be70acef94f4fd7
> > > a6
> > > 6e08d96262d8bf%7C411510044224448aa787d4279c1f087d%7C0%7C0%7C63764899
> > > 89
> > > 66807962%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzI
> > > iL
> > > CJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=TRayRYYU6JoOopJfA9zsp
> > > OI
> > > n%2FGObRgfP2zYF2bS%2BCEA%3D&amp;reserved=0
> > >
> > > >
> > > > Thanks,
> > > > Scott
> > > >
> > >
> >
>

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

Re: [Buildroot] EGLFS Could Not Find DRM Device!

[Charles Steinkuehler]

On 8/28/2021 10:03 PM, Charles Steinkuehler wrote:
> 
> Sorry to jump in, I'm new to Buildroot and this list but I am having the 
> same issue: Using a RPi4 with the latest buildroot (master pulled from 
> git) and no /dev/dri/ devices show up even though config.txt contains:
> 
>     dtoverlay=vc4-kms-v3d-pi4
> 
> ...and the overlay files are present on the first (vfat) partition.
> 
> I started with the raspberrypi4_64_defconfig, switched to glibc, and 
> added a few packages (mesa, kmscube, SDL2).
> 
> On a whim I switched init from the busybox default to systemd (which 
> also pulled in udev), and *PRESTO* I now have a /dev/dri/ folder with 
> devices (after once again adding the config.txt dtoverly line for the 
> kms driver)!
> 
> Is there any documentation about the minimum environment needed to get 
> the vc4-kms drivers running?  Do I need full systemd/udev, is mdev 
> enough, or should devtmpfs be working but perhaps I'm missing something 
> else in the rootfs image?  Is init maybe the problem vs. /dev handling?

Update on what does/doesn't work:

Busybox init + devtmpfs = FAIL
Busybox init + devtmpfs + mdev = FAIL
Busybox init + devtmpfs + eudev = WORKS
systemd + udev = WORKS

I don't know enough about mdev to know if it should be possible to get 
it working vs. eudev.  I may look into that in the future but right now 
I'm just happy to have a system working that doesn't need to pull in all 
of systemd.

For clarity, "WORKS" above means I simply add the 
"dtoverlay=vc4-kms-v3d-pi4" to config.txt, boot, and running "kmscube" 
at the command prompt yields the expected spinning cube.  I also have a 
properly populated /dev/dri, and kmscube reports it is using Broadcom 
V3D 4.2 for OpenGL ES rendering.

-- 
Charles Steinkuehler
charles@steinkuehler.net
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] EGLFS Could Not Find DRM Device!

[Charles Steinkuehler]

> Hello Scott,
> 
> On Wed, 18 Aug 2021 20:28:12 +0000, Scott Bartolett <SBartolett at 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...

Sorry to jump in, I'm new to Buildroot and this list but I am having the 
same issue: Using a RPi4 with the latest buildroot (master pulled from 
git) and no /dev/dri/ devices show up even though config.txt contains:

    dtoverlay=vc4-kms-v3d-pi4

...and the overlay files are present on the first (vfat) partition.

I started with the raspberrypi4_64_defconfig, switched to glibc, and 
added a few packages (mesa, kmscube, SDL2).

On a whim I switched init from the busybox default to systemd (which 
also pulled in udev), and *PRESTO* I now have a /dev/dri/ folder with 
devices (after once again adding the config.txt dtoverly line for the 
kms driver)!

Is there any documentation about the minimum environment needed to get 
the vc4-kms drivers running?  Do I need full systemd/udev, is mdev 
enough, or should devtmpfs be working but perhaps I'm missing something 
else in the rootfs image?  Is init maybe the problem vs. /dev handling?

-- 
Charles Steinkuehler
charles@steinkuehler.net
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot