[Buildroot] libqeglfs.so not found on imx6

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi,

I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
BR2_PACKAGE_QT5BASE_EGLFS

Any idea, did I miss anything?

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi Jagan,

On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
> Hi,
>
> I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
> BR2_PACKAGE_QT5BASE_EGLFS
>
> Any idea, did I miss anything?

Here is a defconfig made for 2016.11.1 version of Buildroot for
Nitrogen6x (i.MX6Q) which has EGLFS support:
http://boundarydevices.com.commondatastorage.googleapis.com/buildroot-v2016.11.1-nitrogen6x-qt5.6.2_defconfig

Please use that config making sure to replace the kernel and u-boot
components for your board first.

Regards,
Gary

[Buildroot] Fwd: libqeglfs.so not found on imx6

[Jagan Teki]

Hi Gary,

On Thu, Mar 2, 2017 at 7:05 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi Jagan,
>
> On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>> Hi,
>>
>> I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
>> BR2_PACKAGE_QT5BASE_EGLFS
>>
>> Any idea, did I miss anything?
>
> Here is a defconfig made for 2016.11.1 version of Buildroot for
> Nitrogen6x (i.MX6Q) which has EGLFS support:
> http://boundarydevices.com.commondatastorage.googleapis.com/buildroot-v2016.11.1-nitrogen6x-qt5.6.2_defconfig

Thanks for the help.

>
> Please use that config making sure to replace the kernel and u-boot
> components for your board first.

Yeah, I was able to build eglfs, and finally I'm launching some demo
application.

# /usr/share/Qtdemo -platform eglfs
QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2
to enable double buffering and vsync.
 If this is not desired, you can override this via: export
QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
Could not open egl display
Aborted

Please let me know if have any idea about this error?

thanks!
--
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.


-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi,

On Thu, Mar 2, 2017 at 6:00 PM, Jagan Teki <jagan@openedev.com> wrote:
>
> Hi Gary,
>
> On Thu, Mar 2, 2017 at 7:05 PM, Gary Bisson
> <gary.bisson@boundarydevices.com> wrote:
> > Hi Jagan,
> >
> > On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> >>
> >> Hi,
> >>
> >> I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
> >> BR2_PACKAGE_QT5BASE_EGLFS
> >>
> >> Any idea, did I miss anything?
> >
> > Here is a defconfig made for 2016.11.1 version of Buildroot for
> > Nitrogen6x (i.MX6Q) which has EGLFS support:
> > http://boundarydevices.com.commondatastorage.googleapis.com/buildroot-v2016.11.1-nitrogen6x-qt5.6.2_defconfig
>
> Thanks for the help.
>
> >
> > Please use that config making sure to replace the kernel and u-boot
> > components for your board first.
>
> Yeah, I was able to build eglfs, and finally I'm launching some demo
> application.

Good.

> # /usr/share/Qtdemo -platform eglfs
> QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2
> to enable double buffering and vsync.
>  If this is not desired, you can override this via: export
> QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
> Could not open egl display
> Aborted
>
> Please let me know if have any idea about this error?

Well have you made sure that your display was properly configured in
the first place?

Are you able to launch the Vivante demos?
(needs BR2_PACKAGE_IMX_GPU_VIV_EXAMPLES)
# cd /usr/share/examples/viv_samples/vdk/
# ./tutorial7

As long as the above isn't working, your Qt app won't work either.

Regards,
Gary

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi Gary,

On Thu, Mar 2, 2017 at 10:34 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi,
>
> On Thu, Mar 2, 2017 at 6:00 PM, Jagan Teki <jagan@openedev.com> wrote:
>>
>> Hi Gary,
>>
>> On Thu, Mar 2, 2017 at 7:05 PM, Gary Bisson
>> <gary.bisson@boundarydevices.com> wrote:
>> > Hi Jagan,
>> >
>> > On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>> >>
>> >> Hi,
>> >>
>> >> I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
>> >> BR2_PACKAGE_QT5BASE_EGLFS
>> >>
>> >> Any idea, did I miss anything?
>> >
>> > Here is a defconfig made for 2016.11.1 version of Buildroot for
>> > Nitrogen6x (i.MX6Q) which has EGLFS support:
>> > http://boundarydevices.com.commondatastorage.googleapis.com/buildroot-v2016.11.1-nitrogen6x-qt5.6.2_defconfig
>>
>> Thanks for the help.
>>
>> >
>> > Please use that config making sure to replace the kernel and u-boot
>> > components for your board first.
>>
>> Yeah, I was able to build eglfs, and finally I'm launching some demo
>> application.
>
> Good.
>
>> # /usr/share/Qtdemo -platform eglfs
>> QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2
>> to enable double buffering and vsync.
>>  If this is not desired, you can override this via: export
>> QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
>> Could not open egl display
>> Aborted
>>
>> Please let me know if have any idea about this error?
>
> Well have you made sure that your display was properly configured in
> the first place?
>
> Are you able to launch the Vivante demos?
> (needs BR2_PACKAGE_IMX_GPU_VIV_EXAMPLES)
> # cd /usr/share/examples/viv_samples/vdk/
> # ./tutorial7
>
> As long as the above isn't working, your Qt app won't work either.

Nothing coming on the display except black screen and 4 penguins at
left top corner.

# cd  /usr/share/examples/viv_samples/vdk/
# ./tutorial7
# ./tutorial7
#

I've built GPU drivers as well, please see below kernel dmesg.

dmesg:
---------
[    1.002652] console [ttymxc3] enabled
[    1.016395] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)
[    1.022660] etnaviv gpu-subsystem: bound 130000.gpu (ops gpu_ops)
[    1.028828] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops)
[    1.035084] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
[    1.093333] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
[    1.145203] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
[    1.151378] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
[    1.159397] [drm] Initialized etnaviv 1.0.0 20151214 for
gpu-subsystem on minor 0
[    1.169491] imx-ipuv3 2400000.ipu: IPUv3H probed
[    1.176314] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    1.183005] [drm] No driver support for vblank timestamp query.
[    1.189462] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops
ipu_crtc_ops)
[    1.197123] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops
ipu_crtc_ops)
[    1.204800] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops
ipu_crtc_ops)
[    1.212462] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops
ipu_crtc_ops)
[    1.220491] imx-drm display-subsystem: bound 2000000.aips-bus:ldb
(ops imx_ldb_ops)
[    1.296817] Console: switching to colour frame buffer device 100x30
[    1.322829] imx-drm display-subsystem: fb0:  frame buffer device
[    1.330623] [drm] Initialized imx-drm 1.0.0 20120507 for
display-subsystem on minor 1
[    1.338579] imx-ipuv3 2800000.ipu: IPUv3H probed

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi Jagan

On Thu, Mar 2, 2017 at 6:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> Hi Gary,
>
> On Thu, Mar 2, 2017 at 10:34 PM, Gary Bisson
> <gary.bisson@boundarydevices.com> wrote:
>> Hi,
>>
>> On Thu, Mar 2, 2017 at 6:00 PM, Jagan Teki <jagan@openedev.com> wrote:
>>>
>>> Hi Gary,
>>>
>>> On Thu, Mar 2, 2017 at 7:05 PM, Gary Bisson
>>> <gary.bisson@boundarydevices.com> wrote:
>>> > Hi Jagan,
>>> >
>>> > On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>> >>
>>> >> Hi,
>>> >>
>>> >> I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
>>> >> BR2_PACKAGE_QT5BASE_EGLFS
>>> >>
>>> >> Any idea, did I miss anything?
>>> >
>>> > Here is a defconfig made for 2016.11.1 version of Buildroot for
>>> > Nitrogen6x (i.MX6Q) which has EGLFS support:
>>> > http://boundarydevices.com.commondatastorage.googleapis.com/buildroot-v2016.11.1-nitrogen6x-qt5.6.2_defconfig
>>>
>>> Thanks for the help.
>>>
>>> >
>>> > Please use that config making sure to replace the kernel and u-boot
>>> > components for your board first.
>>>
>>> Yeah, I was able to build eglfs, and finally I'm launching some demo
>>> application.
>>
>> Good.
>>
>>> # /usr/share/Qtdemo -platform eglfs
>>> QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2
>>> to enable double buffering and vsync.
>>>  If this is not desired, you can override this via: export
>>> QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
>>> Could not open egl display
>>> Aborted
>>>
>>> Please let me know if have any idea about this error?
>>
>> Well have you made sure that your display was properly configured in
>> the first place?
>>
>> Are you able to launch the Vivante demos?
>> (needs BR2_PACKAGE_IMX_GPU_VIV_EXAMPLES)
>> # cd /usr/share/examples/viv_samples/vdk/
>> # ./tutorial7
>>
>> As long as the above isn't working, your Qt app won't work either.
>
> Nothing coming on the display except black screen and 4 penguins at
> left top corner.
>
> # cd  /usr/share/examples/viv_samples/vdk/
> # ./tutorial7
> # ./tutorial7
> #
>
> I've built GPU drivers as well, please see below kernel dmesg.
>
> dmesg:
> ---------
> [    1.002652] console [ttymxc3] enabled
> [    1.016395] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)
> [    1.022660] etnaviv gpu-subsystem: bound 130000.gpu (ops gpu_ops)
> [    1.028828] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops)
> [    1.035084] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
> [    1.093333] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
> [    1.145203] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
> [    1.151378] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
> [    1.159397] [drm] Initialized etnaviv 1.0.0 20151214 for
> gpu-subsystem on minor 0
> [    1.169491] imx-ipuv3 2400000.ipu: IPUv3H probed
> [    1.176314] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [    1.183005] [drm] No driver support for vblank timestamp query.
> [    1.189462] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops
> ipu_crtc_ops)
> [    1.197123] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops
> ipu_crtc_ops)
> [    1.204800] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops
> ipu_crtc_ops)
> [    1.212462] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops
> ipu_crtc_ops)
> [    1.220491] imx-drm display-subsystem: bound 2000000.aips-bus:ldb
> (ops imx_ldb_ops)
> [    1.296817] Console: switching to colour frame buffer device 100x30
> [    1.322829] imx-drm display-subsystem: fb0:  frame buffer device
> [    1.330623] [drm] Initialized imx-drm 1.0.0 20120507 for

I don't know which board you are trying to use but your defconfig is
definitely wrong.
The imx-drm driver is from the mainline kernel and can only work with
Etnaviv, not the Vivante package.

Please check your defconfig.

Regards,
Gary

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> I've built GPU drivers as well, please see below kernel dmesg.
>
> dmesg:
> ---------
> [    1.002652] console [ttymxc3] enabled
> [    1.016395] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)

I see you are using the mainline kernel.

You need to install mesa 17.0.0 and etnaviv gallium drivers (they are
available in the master branch now).

Then you can use kmscube for a quick test to check everything was
properly installed.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi Fabio,

On Thu, Mar 2, 2017 at 10:52 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> I've built GPU drivers as well, please see below kernel dmesg.
>>
>> dmesg:
>> ---------
>> [    1.002652] console [ttymxc3] enabled
>> [    1.016395] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)
>
> I see you are using the mainline kernel.
>
> You need to install mesa 17.0.0 and etnaviv gallium drivers (they are
> available in the master branch now).
>
> Then you can use kmscube for a quick test to check everything was
> properly installed.

This is what the kmscube log shows, used the patch [1]

# kmscube
trying to load module exynos...failed.
trying to load module i915...failed.
trying to load module imx-drm...success.
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
Using display 0x1efa398 with EGL version 1.4
EGL Version "1.4 (DRI2)"
EGL Vendor "Mesa Project"
EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_fence_sync EGL_K
HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EG
L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_KHR_wait_sync
EGL_MESA_configless_context EGL_MESA_dr
m_image EGL_MESA_image_dma_buf_export "
GL Extensions: "(null)"


[1] https://patchwork.ozlabs.org/patch/728156/

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi Gary,

On Thu, Mar 2, 2017 at 10:52 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi Jagan
>
> On Thu, Mar 2, 2017 at 6:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>> Hi Gary,
>>
>> On Thu, Mar 2, 2017 at 10:34 PM, Gary Bisson
>> <gary.bisson@boundarydevices.com> wrote:
>>> Hi,
>>>
>>> On Thu, Mar 2, 2017 at 6:00 PM, Jagan Teki <jagan@openedev.com> wrote:
>>>>
>>>> Hi Gary,
>>>>
>>>> On Thu, Mar 2, 2017 at 7:05 PM, Gary Bisson
>>>> <gary.bisson@boundarydevices.com> wrote:
>>>> > Hi Jagan,
>>>> >
>>>> > On Thu, Mar 2, 2017 at 2:15 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>>> >>
>>>> >> Hi,
>>>> >>
>>>> >> I'm trying to build Qt5 for imx6q sabre and enabled eglfs through
>>>> >> BR2_PACKAGE_QT5BASE_EGLFS
>>>> >>
>>>> >> Any idea, did I miss anything?
>>>> >
>>>> > Here is a defconfig made for 2016.11.1 version of Buildroot for
>>>> > Nitrogen6x (i.MX6Q) which has EGLFS support:
>>>> > http://boundarydevices.com.commondatastorage.googleapis.com/buildroot-v2016.11.1-nitrogen6x-qt5.6.2_defconfig
>>>>
>>>> Thanks for the help.
>>>>
>>>> >
>>>> > Please use that config making sure to replace the kernel and u-boot
>>>> > components for your board first.
>>>>
>>>> Yeah, I was able to build eglfs, and finally I'm launching some demo
>>>> application.
>>>
>>> Good.
>>>
>>>> # /usr/share/Qtdemo -platform eglfs
>>>> QEglFSVivIntegration will set environment variable FB_MULTI_BUFFER=2
>>>> to enable double buffering and vsync.
>>>>  If this is not desired, you can override this via: export
>>>> QT_EGLFS_IMX6_NO_FB_MULTI_BUFFER=1
>>>> Could not open egl display
>>>> Aborted
>>>>
>>>> Please let me know if have any idea about this error?
>>>
>>> Well have you made sure that your display was properly configured in
>>> the first place?
>>>
>>> Are you able to launch the Vivante demos?
>>> (needs BR2_PACKAGE_IMX_GPU_VIV_EXAMPLES)
>>> # cd /usr/share/examples/viv_samples/vdk/
>>> # ./tutorial7
>>>
>>> As long as the above isn't working, your Qt app won't work either.
>>
>> Nothing coming on the display except black screen and 4 penguins at
>> left top corner.
>>
>> # cd  /usr/share/examples/viv_samples/vdk/
>> # ./tutorial7
>> # ./tutorial7
>> #
>>
>> I've built GPU drivers as well, please see below kernel dmesg.
>>
>> dmesg:
>> ---------
>> [    1.002652] console [ttymxc3] enabled
>> [    1.016395] etnaviv gpu-subsystem: bound 134000.gpu (ops gpu_ops)
>> [    1.022660] etnaviv gpu-subsystem: bound 130000.gpu (ops gpu_ops)
>> [    1.028828] etnaviv gpu-subsystem: bound 2204000.gpu (ops gpu_ops)
>> [    1.035084] etnaviv-gpu 134000.gpu: model: GC320, revision: 5007
>> [    1.093333] etnaviv-gpu 130000.gpu: model: GC2000, revision: 5108
>> [    1.145203] etnaviv-gpu 2204000.gpu: model: GC355, revision: 1215
>> [    1.151378] etnaviv-gpu 2204000.gpu: Ignoring GPU with VG and FE2.0
>> [    1.159397] [drm] Initialized etnaviv 1.0.0 20151214 for
>> gpu-subsystem on minor 0
>> [    1.169491] imx-ipuv3 2400000.ipu: IPUv3H probed
>> [    1.176314] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
>> [    1.183005] [drm] No driver support for vblank timestamp query.
>> [    1.189462] imx-drm display-subsystem: bound imx-ipuv3-crtc.2 (ops
>> ipu_crtc_ops)
>> [    1.197123] imx-drm display-subsystem: bound imx-ipuv3-crtc.3 (ops
>> ipu_crtc_ops)
>> [    1.204800] imx-drm display-subsystem: bound imx-ipuv3-crtc.6 (ops
>> ipu_crtc_ops)
>> [    1.212462] imx-drm display-subsystem: bound imx-ipuv3-crtc.7 (ops
>> ipu_crtc_ops)
>> [    1.220491] imx-drm display-subsystem: bound 2000000.aips-bus:ldb
>> (ops imx_ldb_ops)
>> [    1.296817] Console: switching to colour frame buffer device 100x30
>> [    1.322829] imx-drm display-subsystem: fb0:  frame buffer device
>> [    1.330623] [drm] Initialized imx-drm 1.0.0 20120507 for
>
> I don't know which board you are trying to use but your defconfig is
> definitely wrong.
> The imx-drm driver is from the mainline kernel and can only work with
> Etnaviv, not the Vivante package.

Yes, I understand. Thanks for the help.

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Thu, Mar 2, 2017 at 2:56 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> This is what the kmscube log shows, used the patch [1]

Log looks good.

Do you see the cube spinning?

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Thu, Mar 2, 2017 at 11:29 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Thu, Mar 2, 2017 at 2:56 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> This is what the kmscube log shows, used the patch [1]
>
> Log looks good.
>
> Do you see the cube spinning?

No, I didn't see any cubes..before running kmscube it was black screen
with penguins once I ran kmscube red flash then black screen (no
penguins)

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Thu, Mar 2, 2017 at 3:02 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> No, I didn't see any cubes..before running kmscube it was black screen
> with penguins once I ran kmscube red flash then black screen (no
> penguins)

Which kernel version are you using? Could you try the latest 4.9 or 4.10?

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Thu, Mar 2, 2017 at 11:34 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Thu, Mar 2, 2017 at 3:02 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> No, I didn't see any cubes..before running kmscube it was black screen
>> with penguins once I ran kmscube red flash then black screen (no
>> penguins)
>
> Which kernel version are you using? Could you try the latest 4.9 or 4.10?

Linux version 4.10.0-rc8-next-20170217-00002-g5c07a3d-dirty

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Thu, Mar 2, 2017 at 3:06 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> Linux version 4.10.0-rc8-next-20170217-00002-g5c07a3d-dirty

Well, not a very stable kernel base :-)

I would recommend you to trying 4.9.13 or 4.10.1.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Thu, Mar 2, 2017 at 11:37 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Thu, Mar 2, 2017 at 3:06 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> Linux version 4.10.0-rc8-next-20170217-00002-g5c07a3d-dirty
>
> Well, not a very stable kernel base :-)
>
> I would recommend you to trying 4.9.13 or 4.10.1.

Yeah, I've tried 4.10.1 same issue but some how bigger red flash
compared to previous.


Log:
# cat /proc/version
Linux version 4.10.1 (root at d7d7e20b645f) (gcc version 4.9.0 (GCC) ) #1
SMP Thu Mar 2 18:23:17 UTC 2017
# kmscube
trying to load module exynos...failed.
trying to load module i915...failed.
trying to load module imx-drm...success.
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
Using display 0x105a398 with EGL version 1.4
EGL Version "1.4 (DRI2)"
EGL Vendor "Mesa Project"
EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_fence_sync EGL_K
HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EG
L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_KHR_wait_sync
EGL_MESA_configless_context EGL_MESA_dr
m_image EGL_MESA_image_dma_buf_export "
GL Extensions: "(null)"


-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Thu, Mar 2, 2017 at 11:58 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> On Thu, Mar 2, 2017 at 11:37 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Thu, Mar 2, 2017 at 3:06 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>>> Linux version 4.10.0-rc8-next-20170217-00002-g5c07a3d-dirty
>>
>> Well, not a very stable kernel base :-)
>>
>> I would recommend you to trying 4.9.13 or 4.10.1.
>
> Yeah, I've tried 4.10.1 same issue but some how bigger red flash
> compared to previous.
>
>
> Log:
> # cat /proc/version
> Linux version 4.10.1 (root at d7d7e20b645f) (gcc version 4.9.0 (GCC) ) #1
> SMP Thu Mar 2 18:23:17 UTC 2017
> # kmscube
> trying to load module exynos...failed.
> trying to load module i915...failed.
> trying to load module imx-drm...success.
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> Using display 0x105a398 with EGL version 1.4
> EGL Version "1.4 (DRI2)"
> EGL Vendor "Mesa Project"
> EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
> EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
> EGL_KHR_fence_sync EGL_K
> HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
> EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
> EGL_KHR_image EGL_KHR_image_base EG
> L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
> EGL_KHR_surfaceless_context EGL_KHR_wait_sync
> EGL_MESA_configless_context EGL_MESA_dr
> m_image EGL_MESA_image_dma_buf_export "
> GL Extensions: "(null)"

I've some more verbose info on another display.

Log:
----
# cat /proc/version
Linux version 4.10.1 (root at d7d7e20b645f) (gcc version 4.9.0 (GCC) ) #1
SMP Thu Mar 2 18:23:17 UTC 2017
# kmscube
trying to load module exynos...failed.
trying to load module i915...failed.
trying to load module imx-drm...success.
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
Using display 0x922398 with EGL version 1.4
EGL Version "1.4 (DRI2)"
EGL Vendor "Mesa Project"
EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_fence_sync EGL_K
HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EG
L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_KHR_wait_sync
EGL_MESA_configless_context EGL_MESA_dr
m_image EGL_MESA_image_dma_buf_export "
GL Extensions: "(null)"
[   87.631131] ------------[ cut here ]------------
[   87.635799] WARNING: CPU: 2 PID: 275 at
drivers/gpu/drm/drm_atomic_helper.c:1149
drm_atomic_helper_wait_for_vblanks+0x218/0x228
[   87.647319] [CRTC:26] vblank wait timed out
[   87.651536] Modules linked in:
[   87.654610] CPU: 2 PID: 275 Comm: kmscube Tainted: G        W       4.10.1 #1
[   87.661751] Hardware name: Freescale i.MX6 Quad/DualLite (Device Tree)
[   87.668282] Backtrace:
[   87.670753] [<c010c490>] (dump_backtrace) from [<c010c738>]
(show_stack+0x18/0x1c)
[   87.678333]  r6:60070013 r5:00000000 r4:c0e29318 r3:00000000
[   87.684006] [<c010c720>] (show_stack) from [<c03fe09c>]
(dump_stack+0xb4/0xe8)
[   87.691241] [<c03fdfe8>] (dump_stack) from [<c0126114>] (__warn+0xd8/0x104)
[   87.698212]  r10:00000000 r9:c04d3e50 r8:0000047d r7:00000009
r6:c0c1ea40 r5:00000000
[   87.706048]  r4:ee4ffc98 r3:00000000
[   87.709633] [<c012603c>] (__warn) from [<c0126180>]
(warn_slowpath_fmt+0x40/0x48)
[   87.717126]  r9:ee832018 r8:00000000 r7:ee831800 r6:ee514400
r5:ee4d3c40 r4:c0c1eb5c
[   87.724880] [<c0126144>] (warn_slowpath_fmt) from [<c04d3e50>]
(drm_atomic_helper_wait_for_vblanks+0x218/0x228)
[   87.734973]  r3:0000001a r2:c0c1eb5c
[   87.738552]  r4:00000000
[   87.741101] [<c04d3c38>] (drm_atomic_helper_wait_for_vblanks) from
[<c0500574>] (imx_drm_atomic_commit_tail+0x50/0x60)
[   87.751805]  r10:ee4ffe58 r9:ef33a020 r8:ee089140 r7:ee831800
r6:00000000 r5:ee831800
[   87.759638]  r4:ee4d3c40
[   87.762182] [<c0500524>] (imx_drm_atomic_commit_tail) from
[<c04d4530>] (commit_tail+0x4c/0x94)
[   87.770886]  r5:c0e3a4e8 r4:ee4d3c40
[   87.774474] [<c04d44e4>] (commit_tail) from [<c04d659c>]
(drm_atomic_helper_commit+0xd0/0x1ac)
[   87.783090]  r5:00000000 r4:ee4d3c40
[   87.786680] [<c04d64cc>] (drm_atomic_helper_commit) from
[<c04f4bb8>] (drm_atomic_commit+0x54/0x60)
[   87.795732]  r7:ee4ffdd8 r6:ee831800 r5:ee4d3c40 r4:00000000
[   87.801402] [<c04f4b64>] (drm_atomic_commit) from [<c04d6b98>]
(drm_atomic_helper_set_config+0x80/0xd0)
[   87.810801]  r6:ee832018 r5:00000000 r4:ee4d3c40 r3:00000004
[   87.816476] [<c04d6b18>] (drm_atomic_helper_set_config) from
[<c04e91cc>] (drm_mode_set_config_internal+0x60/0xe4)
[   87.826831]  r7:ee089140 r6:eebe4000 r5:ee832018 r4:ee0c09c0
[   87.832501] [<c04e916c>] (drm_mode_set_config_internal) from
[<c04e9b08>] (drm_mode_setcrtc+0x434/0x498)
[   87.841987]  r7:ee089140 r6:eebe4000 r5:ee831800 r4:00000001
[   87.847656] [<c04e96d4>] (drm_mode_setcrtc) from [<c04e1624>]
(drm_ioctl+0x21c/0x458)
[   87.855495]  r10:c06864a2 r9:ee515a00 r8:c0a40420 r7:00000068
r6:ee4ffe58 r5:00000068
[   87.863329]  r4:00000000
[   87.865877] [<c04e1408>] (drm_ioctl) from [<c0235608>]
(do_vfs_ioctl+0x98/0xa2c)
[   87.873282]  r10:00000000 r9:ee4fe000 r8:c0235fd8 r7:00000003
r6:ee45d540 r5:ef31b768
[   87.881115]  r4:bed94ab0
[   87.883661] [<c0235570>] (do_vfs_ioctl) from [<c0235fd8>]
(SyS_ioctl+0x3c/0x64)
[   87.890978]  r10:00000000 r9:ee4fe000 r8:00000003 r7:c06864a2
r6:ee45d540 r5:bed94ab0
[   87.898812]  r4:ee45d540
[   87.901359] [<c0235f9c>] (SyS_ioctl) from [<c0107ea0>]
(ret_fast_syscall+0x0/0x1c)
[   87.908937]  r8:c0108044 r7:00000036 r6:c06864a2 r5:00000003
r4:bed94ab0 r3:00000001
[   87.916798] ---[ end trace 7f71ee8af7dd698c ]---


thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Thu, Mar 2, 2017 at 3:32 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> [   87.631131] ------------[ cut here ]------------
> [   87.635799] WARNING: CPU: 2 PID: 275 at
> drivers/gpu/drm/drm_atomic_helper.c:1149
> drm_atomic_helper_wait_for_vblanks+0x218/0x228
> [   87.647319] [CRTC:26] vblank wait timed out

I think Phillip Zabel posted a recent series to address this issue 4.10 issue.

Does kmscube work on 4.9.13 for you?

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Mar 3, 2017 12:06 AM, "Fabio Estevam" <festevam@gmail.com> wrote:

On Thu, Mar 2, 2017 at 3:32 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> [   87.631131] ------------[ cut here ]------------
> [   87.635799] WARNING: CPU: 2 PID: 275 at
> drivers/gpu/drm/drm_atomic_helper.c:1149
> drm_atomic_helper_wait_for_vblanks+0x218/0x228
> [   87.647319] [CRTC:26] vblank wait timed out

I think Phillip Zabel posted a recent series to address this issue 4.10
issue.

Does kmscube work on 4.9.13 for you?


Will check and let you know.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20170303/cbfe8359/attachment.html>

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Fri, Mar 3, 2017 at 12:11 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>
> On Mar 3, 2017 12:06 AM, "Fabio Estevam" <festevam@gmail.com> wrote:
>
> On Thu, Mar 2, 2017 at 3:32 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> [   87.631131] ------------[ cut here ]------------
>> [   87.635799] WARNING: CPU: 2 PID: 275 at
>> drivers/gpu/drm/drm_atomic_helper.c:1149
>> drm_atomic_helper_wait_for_vblanks+0x218/0x228
>> [   87.647319] [CRTC:26] vblank wait timed out
>
> I think Phillip Zabel posted a recent series to address this issue 4.10
> issue.
>
> Does kmscube work on 4.9.13 for you?

No, still same.

# cat /proc/version
Linux version 4.9.13 (root at 261fc421fda2) (gcc version 4.9.0 (GCC) ) #1
SMP Fri Mar 3 05:56:41 UTC 2017
# kmscube
trying to load module exynos...failed.
trying to load module i915...failed.
trying to load module imx-drm...success.
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
Using display 0x606548 with EGL version 1.4
EGL Version "1.4 (DRI2)"
EGL Vendor "Mesa Project"
EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_fence_sync EGL_K
HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EG
L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_KHR_wait_sync
EGL_MESA_configless_context EGL_MESA_dr
m_image EGL_MESA_image_dma_buf_export "
GL Extensions: "(null)"
^C[   63.353491] imx-ipuv3 2400000.ipu: videomode adapted for IPU restrictions
[   63.360573] imx-ipuv3 2400000.ipu: videomode adapted for IPU restrictions

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi Fabio,

On Fri, Mar 3, 2017 at 12:22 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> On Fri, Mar 3, 2017 at 12:11 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>>
>> On Mar 3, 2017 12:06 AM, "Fabio Estevam" <festevam@gmail.com> wrote:
>>
>> On Thu, Mar 2, 2017 at 3:32 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>>> [   87.631131] ------------[ cut here ]------------
>>> [   87.635799] WARNING: CPU: 2 PID: 275 at
>>> drivers/gpu/drm/drm_atomic_helper.c:1149
>>> drm_atomic_helper_wait_for_vblanks+0x218/0x228
>>> [   87.647319] [CRTC:26] vblank wait timed out
>>
>> I think Phillip Zabel posted a recent series to address this issue 4.10
>> issue.
>>
>> Does kmscube work on 4.9.13 for you?
>
> No, still same.
>
> # cat /proc/version
> Linux version 4.9.13 (root at 261fc421fda2) (gcc version 4.9.0 (GCC) ) #1
> SMP Fri Mar 3 05:56:41 UTC 2017
> # kmscube
> trying to load module exynos...failed.
> trying to load module i915...failed.
> trying to load module imx-drm...success.
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> Using display 0x606548 with EGL version 1.4
> EGL Version "1.4 (DRI2)"
> EGL Vendor "Mesa Project"
> EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
> EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
> EGL_KHR_fence_sync EGL_K
> HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
> EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
> EGL_KHR_image EGL_KHR_image_base EG
> L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
> EGL_KHR_surfaceless_context EGL_KHR_wait_sync
> EGL_MESA_configless_context EGL_MESA_dr
> m_image EGL_MESA_image_dma_buf_export "
> GL Extensions: "(null)"
> ^C[   63.353491] imx-ipuv3 2400000.ipu: videomode adapted for IPU restrictions
> [   63.360573] imx-ipuv3 2400000.ipu: videomode adapted for IPU restrictions

Got the cube running..

Log:
----
# kmscube
trying to load module exynos...failed.
trying to load module i915...failed.
trying to load module imx-drm...success.
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
Using display 0x1258ef8 with EGL version 1.4
EGL Version "1.4 (DRI2)"
EGL Vendor "Mesa Project"
EGL Extensions "EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context
EGL_KHR_fence_sync EGL_K
HR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image
EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image
EGL_KHR_image EGL_KHR_image_base EG
L_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync
EGL_KHR_surfaceless_context EGL_KHR_wait_sync
EGL_MESA_configless_context EGL_MESA_dr
m_image EGL_MESA_image_dma_buf_export "
GL Extensions: "GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888
GL_OES_compressed_ETC1_RGB
8_texture GL_OES_depth24 GL_OES_element_index_uint
GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8
GL_OES_standard_derivatives GL_OES_stenci
l8 GL_OES_texture_3D GL_OES_texture_npot GL_OES_vertex_half_float
GL_OES_EGL_image GL_OES_depth_texture GL_OES_packed_depth_stencil
GL_EXT_texture_type_
2_10_10_10_REV GL_OES_get_program_binary GL_APPLE_texture_max_level
GL_EXT_discard_framebuffer GL_EXT_read_format_bgra
GL_NV_fbo_color_attachments GL_OE
S_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object
GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer
GL_NV_read_depth GL_NV_read_
depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers
GL_EXT_map_buffer_range GL_KHR_debug GL_OES_surfaceless_context
GL_EXT_separate_shader_objects GL_E
XT_draw_elements_base_vertex GL_EXT_texture_border_clamp
GL_KHR_context_flush_control GL_OES_draw_elements_base_vertex
GL_OES_texture_border_clamp "

Missing openGL libs in previous build.

Thank you!

-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

Hi Jagan,

On Fri, Mar 3, 2017 at 8:19 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> Got the cube running..

Excellent. If you manage to get QT working accelerated by Etnaviv,
please let us know.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi Fabio,

On Fri, Mar 3, 2017 at 5:17 PM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Jagan,
>
> On Fri, Mar 3, 2017 at 8:19 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
>> Got the cube running..
>
> Excellent. If you manage to get QT working accelerated by Etnaviv,
> please let us know.

Sure, I'm trying to play some graphic video like CinematicExperience
but look like some issue on eglfs.

# /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
qt.qpa.egldeviceintegration: Failed to load EGL device integration "eglfs_kms"
qt.qpa.egldeviceintegration: Failed to load EGL device integration
"eglfs_kms_egldevice"
Could not open display
Aborted

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi

On Fri, Mar 3, 2017 at 5:20 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
> Hi Fabio,
>
> On Fri, Mar 3, 2017 at 5:17 PM, Fabio Estevam <festevam@gmail.com> wrote:
> > Hi Jagan,
> >
> > On Fri, Mar 3, 2017 at 8:19 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> >
> >> Got the cube running..
> >
> > Excellent. If you manage to get QT working accelerated by Etnaviv,
> > please let us know.
>
> Sure, I'm trying to play some graphic video like CinematicExperience
> but look like some issue on eglfs.
>
> # /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
> qt.qpa.egldeviceintegration: Failed to load EGL device integration "eglfs_kms"
> qt.qpa.egldeviceintegration: Failed to load EGL device integration
> "eglfs_kms_egldevice"
> Could not open display
> Aborted

I've had Qt5 and EGLFS running on Etnaviv before (an image is
available on our website).

Here was the buildroot defconfig:
http://linode.boundarydevices.com/buildroot_gst1_etnaviv_qt5_defconfig

Note that the cinematics demo doesn't show great performances.

Regards,
Gary

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

Hi Gary,

On Fri, Mar 3, 2017 at 10:37 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi
>
> On Fri, Mar 3, 2017 at 5:20 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>> Hi Fabio,
>>
>> On Fri, Mar 3, 2017 at 5:17 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> > Hi Jagan,
>> >
>> > On Fri, Mar 3, 2017 at 8:19 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>> >
>> >> Got the cube running..
>> >
>> > Excellent. If you manage to get QT working accelerated by Etnaviv,
>> > please let us know.
>>
>> Sure, I'm trying to play some graphic video like CinematicExperience
>> but look like some issue on eglfs.
>>
>> # /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
>> qt.qpa.egldeviceintegration: Failed to load EGL device integration "eglfs_kms"
>> qt.qpa.egldeviceintegration: Failed to load EGL device integration
>> "eglfs_kms_egldevice"
>> Could not open display
>> Aborted
>
> I've had Qt5 and EGLFS running on Etnaviv before (an image is
> available on our website).

Oh., thanks for the info. Can you point me demo link that you tried?

>
> Here was the buildroot defconfig:
> http://linode.boundarydevices.com/buildroot_gst1_etnaviv_qt5_defconfig

Sure, I will take this reference.

> Note that the cinematics demo doesn't show great performances.

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi,

On Fri, Mar 3, 2017 at 6:37 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> Hi Gary,
>
> On Fri, Mar 3, 2017 at 10:37 PM, Gary Bisson
> <gary.bisson@boundarydevices.com> wrote:
>> Hi
>>
>> On Fri, Mar 3, 2017 at 5:20 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>>
>>> Hi Fabio,
>>>
>>> On Fri, Mar 3, 2017 at 5:17 PM, Fabio Estevam <festevam@gmail.com> wrote:
>>> > Hi Jagan,
>>> >
>>> > On Fri, Mar 3, 2017 at 8:19 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>> >
>>> >> Got the cube running..
>>> >
>>> > Excellent. If you manage to get QT working accelerated by Etnaviv,
>>> > please let us know.
>>>
>>> Sure, I'm trying to play some graphic video like CinematicExperience
>>> but look like some issue on eglfs.
>>>
>>> # /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
>>> qt.qpa.egldeviceintegration: Failed to load EGL device integration "eglfs_kms"
>>> qt.qpa.egldeviceintegration: Failed to load EGL device integration
>>> "eglfs_kms_egldevice"
>>> Could not open display
>>> Aborted
>>
>> I've had Qt5 and EGLFS running on Etnaviv before (an image is
>> available on our website).
>
> Oh., thanks for the info. Can you point me demo link that you tried?

https://boundarydevices.com/pengutronix-etnaviv-demo-nitrogen6x/

At the end of the article is a link to the image. Works on all BD
Nitrogen platforms (and SabreLite).

Regards,
Gary

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

Hi Gary,

On Fri, Mar 3, 2017 at 2:07 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:

> Here was the buildroot defconfig:
> http://linode.boundarydevices.com/buildroot_gst1_etnaviv_qt5_defconfig
>
> Note that the cinematics demo doesn't show great performances.

Just tried your defconfig on top of master. Could not get Qt5.8 to
build, so I switched to Qt5.6.

Here is my defconfig:
http://pastebin.com/Fy4rZCHY

When I try to run the demo:

#  /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
drmModeGetResources failed
Segmentation fault
#

Any ideas?

Thanks

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Fri, Mar 3, 2017 at 8:00 PM, Fabio Estevam <festevam@gmail.com> wrote:

> Just tried your defconfig on top of master. Could not get Qt5.8 to
> build, so I switched to Qt5.6.
>
> Here is my defconfig:
> http://pastebin.com/Fy4rZCHY
>
> When I try to run the demo:
>
> #  /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> drmModeGetResources failed
> Segmentation fault
> #
>
> Any ideas?

Here is the strace output:
http://pastebin.com/dgjFA3Dm

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi Fabio,

On Sat, Mar 4, 2017 at 2:48 AM, Fabio Estevam <festevam@gmail.com> wrote:
> On Fri, Mar 3, 2017 at 8:00 PM, Fabio Estevam <festevam@gmail.com> wrote:
>
>> Just tried your defconfig on top of master. Could not get Qt5.8 to
>> build, so I switched to Qt5.6.

I've seen that issue too actually when testing mesa17.0, qtbase 5.8
wouldn't build. Didn't have time to investigate yet.

>> Here is my defconfig:
>> http://pastebin.com/Fy4rZCHY
>>
>> When I try to run the demo:
>>
>> #  /usr/share/Qt5/CinematicExperience/Qt5_CinematicExperience
>> MESA-LOADER: device is not located on the PCI bus
>> MESA-LOADER: device is not located on the PCI bus
>> MESA-LOADER: device is not located on the PCI bus
>> drmModeGetResources failed
>> Segmentation fault
>> #
>>
>> Any ideas?
>
> Here is the strace output:
> http://pastebin.com/dgjFA3Dm

I actually got pretty lucky I guess, when I tried (before mesa17, with
Christian's tree) it just worked out of the box.

Have you made any progress?

Regards,
Gary

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

Hi Gary,

On Sat, Mar 4, 2017 at 9:27 AM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:

> I actually got pretty lucky I guess, when I tried (before mesa17, with
> Christian's tree) it just worked out of the box.
>
> Have you made any progress?

Not yet, still stuck at the "drmModeGetResources failed" error.

Thanks

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

Hi Gary,

On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:

> Not yet, still stuck at the "drmModeGetResources failed" error.

I can also get this same error with the new kmscube package from:
https://cgit.freedesktop.org/mesa/kmscube/log/

# kmscube
drmModeGetResources failed: Invalid argument
failed to initialize legacy DRM

It works if I explicitly pass the /dev/dri device:

kmscube -D /dev/dri/card1

I think QT5 is trying to access /dev/dri/card0, but it should be using
/dev/dri/card1 instead.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
> Hi Gary,
>
> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:
>
>> Not yet, still stuck at the "drmModeGetResources failed" error.
>
> I can also get this same error with the new kmscube package from:
> https://cgit.freedesktop.org/mesa/kmscube/log/
>
> # kmscube
> drmModeGetResources failed: Invalid argument
> failed to initialize legacy DRM
>
> It works if I explicitly pass the /dev/dri device:
>
> kmscube -D /dev/dri/card1
>
> I think QT5 is trying to access /dev/dri/card0, but it should be using
> /dev/dri/card1 instead.

Yes, this is the problem.

If I do an ugly hack like this:

--- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
+++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
@@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
     Q_ASSERT(m_gbm_device == Q_NULLPTR);

     qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
-    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
| O_CLOEXEC);
+    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
     if (m_dri_fd == -1) {
         qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
         return false;
-- 
2.7.4

Then the demo is launched. It still do not run very well, but@least
it starts.

Does anyone have an idea on what would be a proper fix?

Thanks

[Buildroot] libqeglfs.so not found on imx6

[Gary Bisson]

Hi Fabio,

On Sat, Mar 4, 2017 at 8:41 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
>> Hi Gary,
>>
>> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>
>>> Not yet, still stuck at the "drmModeGetResources failed" error.
>>
>> I can also get this same error with the new kmscube package from:
>> https://cgit.freedesktop.org/mesa/kmscube/log/
>>
>> # kmscube
>> drmModeGetResources failed: Invalid argument
>> failed to initialize legacy DRM
>>
>> It works if I explicitly pass the /dev/dri device:
>>
>> kmscube -D /dev/dri/card1
>>
>> I think QT5 is trying to access /dev/dri/card0, but it should be using
>> /dev/dri/card1 instead.
>
> Yes, this is the problem.
>
> If I do an ugly hack like this:
>
> --- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
> +++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
> @@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
>      Q_ASSERT(m_gbm_device == Q_NULLPTR);
>
>      qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
> -    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
> | O_CLOEXEC);
> +    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
>      if (m_dri_fd == -1) {
>          qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
>          return false;
> --
> 2.7.4
>
> Then the demo is launched. It still do not run very well, but at least
> it starts.
>
> Does anyone have an idea on what would be a proper fix?

That's strange I didn't have to do that. Worst part is that my demo
image is using Qt5.6.2 (same as your image) and that I checked no
special env variable is set.

Maybe you can try your kernel on my image, see if that works.

Regards,
Gary

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Mon, Mar 6, 2017 at 3:49 PM, Gary Bisson
<gary.bisson@boundarydevices.com> wrote:
> Hi Fabio,
>
> On Sat, Mar 4, 2017 at 8:41 PM, Fabio Estevam <festevam@gmail.com> wrote:
>> On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>> Hi Gary,
>>>
>>> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>>
>>>> Not yet, still stuck at the "drmModeGetResources failed" error.
>>>
>>> I can also get this same error with the new kmscube package from:
>>> https://cgit.freedesktop.org/mesa/kmscube/log/
>>>
>>> # kmscube
>>> drmModeGetResources failed: Invalid argument
>>> failed to initialize legacy DRM
>>>
>>> It works if I explicitly pass the /dev/dri device:
>>>
>>> kmscube -D /dev/dri/card1
>>>
>>> I think QT5 is trying to access /dev/dri/card0, but it should be using
>>> /dev/dri/card1 instead.
>>
>> Yes, this is the problem.
>>
>> If I do an ugly hack like this:
>>
>> --- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>> +++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>> @@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
>>      Q_ASSERT(m_gbm_device == Q_NULLPTR);
>>
>>      qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
>> -    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
>> | O_CLOEXEC);
>> +    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
>>      if (m_dri_fd == -1) {
>>          qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
>>          return false;
>> --
>> 2.7.4
>>
>> Then the demo is launched. It still do not run very well, but at least
>> it starts.
>>
>> Does anyone have an idea on what would be a proper fix?
>
> That's strange I didn't have to do that. Worst part is that my demo
> image is using Qt5.6.2 (same as your image) and that I checked no
> special env variable is set.
>
> Maybe you can try your kernel on my image, see if that works.

I just used rootfs, from the link, and kernel 4.9.13 mainline.

Able to see the demo nicely.

Order:
- kmscube
- Boundary devices Tux
- jellyfish
- ideas in motion
- 28 fps (1. Lord of the Rings)

So, I'm investigating config options on buildroot will let you know
for further update.

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Mon, Mar 6, 2017 at 4:33 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> On Mon, Mar 6, 2017 at 3:49 PM, Gary Bisson
> <gary.bisson@boundarydevices.com> wrote:
>> Hi Fabio,
>>
>> On Sat, Mar 4, 2017 at 8:41 PM, Fabio Estevam <festevam@gmail.com> wrote:
>>> On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>>> Hi Gary,
>>>>
>>>> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:
>>>>
>>>>> Not yet, still stuck at the "drmModeGetResources failed" error.
>>>>
>>>> I can also get this same error with the new kmscube package from:
>>>> https://cgit.freedesktop.org/mesa/kmscube/log/
>>>>
>>>> # kmscube
>>>> drmModeGetResources failed: Invalid argument
>>>> failed to initialize legacy DRM
>>>>
>>>> It works if I explicitly pass the /dev/dri device:
>>>>
>>>> kmscube -D /dev/dri/card1
>>>>
>>>> I think QT5 is trying to access /dev/dri/card0, but it should be using
>>>> /dev/dri/card1 instead.
>>>
>>> Yes, this is the problem.
>>>
>>> If I do an ugly hack like this:
>>>
>>> --- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>>> +++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
>>> @@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
>>>      Q_ASSERT(m_gbm_device == Q_NULLPTR);
>>>
>>>      qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
>>> -    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
>>> | O_CLOEXEC);
>>> +    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
>>>      if (m_dri_fd == -1) {
>>>          qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
>>>          return false;
>>> --
>>> 2.7.4
>>>
>>> Then the demo is launched. It still do not run very well, but at least
>>> it starts.
>>>
>>> Does anyone have an idea on what would be a proper fix?
>>
>> That's strange I didn't have to do that. Worst part is that my demo
>> image is using Qt5.6.2 (same as your image) and that I checked no
>> special env variable is set.
>>
>> Maybe you can try your kernel on my image, see if that works.
>
> I just used rootfs, from the link, and kernel 4.9.13 mainline.
>
> Able to see the demo nicely.
>
> Order:
> - kmscube
> - Boundary devices Tux
> - jellyfish
> - ideas in motion
> - 28 fps (1. Lord of the Rings)
>
> So, I'm investigating config options on buildroot will let you know
> for further update.

And by the way, did anyone find this issue.

In file included from
/workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/egl.h:39:0,
                 from
../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/../../../../../src/platformsupport/eglconvenience/qt_egl_p.h:63,
                 from
../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/qt_egl_p.h:1,
                 from api/qeglfsglobal_p.h:56,
                 from api/qeglfsintegration_p.h:54,
                 from qeglfsmain.cpp:41:
/workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/eglplatform.h:119:22:
fatal error: X11/Xlib.h: No such file or directory
 #include <X11/Xlib.h>
                      ^
compilation terminated.

Look like Qt5.8.0 is unable to build with current tool-chain, 5.6.2 succeeded

thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Mon, Mar 6, 2017 at 8:44 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>
> And by the way, did anyone find this issue.
>
> In file included from
> /workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/egl.h:39:0,
>                  from
> ../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/../../../../../src/platformsupport/eglconvenience/qt_egl_p.h:63,
>                  from
> ../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/qt_egl_p.h:1,
>                  from api/qeglfsglobal_p.h:56,
>                  from api/qeglfsintegration_p.h:54,
>                  from qeglfsmain.cpp:41:
> /workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/eglplatform.h:119:22:
> fatal error: X11/Xlib.h: No such file or directory
>  #include <X11/Xlib.h>
>                       ^
> compilation terminated.
>
> Look like Qt5.8.0 is unable to build with current tool-chain, 5.6.2 succeeded

Yes, that's why I needed to switch to QT 5.6.2 on my tests.

I would be interested to know if you are able to run the Qt5 Cinematic
demo well when building it from Buildroot master.

Thanks

[Buildroot] libqeglfs.so not found on imx6

[Jagan Teki]

On Mon, Mar 6, 2017 at 5:16 PM, Fabio Estevam <festevam@gmail.com> wrote:
> On Mon, Mar 6, 2017 at 8:44 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
>>
>> And by the way, did anyone find this issue.
>>
>> In file included from
>> /workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/egl.h:39:0,
>>                  from
>> ../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/../../../../../src/platformsupport/eglconvenience/qt_egl_p.h:63,
>>                  from
>> ../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/qt_egl_p.h:1,
>>                  from api/qeglfsglobal_p.h:56,
>>                  from api/qeglfsintegration_p.h:54,
>>                  from qeglfsmain.cpp:41:
>> /workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/eglplatform.h:119:22:
>> fatal error: X11/Xlib.h: No such file or directory
>>  #include <X11/Xlib.h>
>>                       ^
>> compilation terminated.
>>
>> Look like Qt5.8.0 is unable to build with current tool-chain, 5.6.2 succeeded
>
> Yes, that's why I needed to switch to QT 5.6.2 on my tests.
>
> I would be interested to know if you are able to run the Qt5 Cinematic
> demo well when building it from Buildroot master.

- Jelly fish: working
-------------------------
# glmark2-es2-drm -b jellyfish
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
** Failed to set swap interval. Results may be bounded above by refresh rate.
=======================================================
    glmark2 2014.03
=======================================================
    OpenGL Information
    GL_VENDOR:     etnaviv
    GL_RENDERER:   Gallium 0.4 on Vivante GC2000 rev 5108
    GL_VERSION:    OpenGL ES 2.0 Mesa 17.0.1
=======================================================
** Failed to set swap interval. Results may be bounded above by refresh rate.
[jellyfish] <default>: FPS: 25 FrameTime: 40.000 ms
================================

- CinematicExperience:
-----------------------------
- demo launched but 'Black' object on list like 'Lord of the Rings' etc

# CinematicExperience-demo
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
MESA-LOADER: device is not located on the PCI bus
Failed to move cursor on screen LVDS1: -14
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
QOpenGLFramebufferObject: Unsupported framebuffer format.
QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.


thanks!
-- 
Jagan Teki
Free Software Engineer | www.openedev.com
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

On Mon, Mar 6, 2017 at 9:08 AM, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> - CinematicExperience:
> -----------------------------
> - demo launched but 'Black' object on list like 'Lord of the Rings' etc
>
> # CinematicExperience-demo
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> MESA-LOADER: device is not located on the PCI bus
> Failed to move cursor on screen LVDS1: -14
> libpng warning: iCCP: known incorrect sRGB profile
> libpng warning: iCCP: known incorrect sRGB profile
> QOpenGLFramebufferObject: Unsupported framebuffer format.
> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
> QOpenGLFramebufferObject: Unsupported framebuffer format.
> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
> QOpenGLFramebufferObject: Unsupported framebuffer format.
> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.
> QOpenGLFramebufferObject: Unsupported framebuffer format.
> QOpenGLFramebufferObject: Framebuffer incomplete, missing attachment.

I also saw this defect here. Would be nice to understand where it comes from.

Gary,

Do you have the Buildroot hash that your demo was generated from?

Thanks

[Buildroot] libqeglfs.so not found on imx6

[Peter Seiderer]

Hello Jagan,

On Mon, 6 Mar 2017 17:14:23 +0530, Jagan Teki <jagannadh.teki@gmail.com> wrote:

> On Mon, Mar 6, 2017 at 4:33 PM, Jagan Teki <jagannadh.teki@gmail.com> wrote:
> > On Mon, Mar 6, 2017 at 3:49 PM, Gary Bisson
> > <gary.bisson@boundarydevices.com> wrote:
> >> Hi Fabio,
> >>
> >> On Sat, Mar 4, 2017 at 8:41 PM, Fabio Estevam <festevam@gmail.com> wrote:
> >>> On Sat, Mar 4, 2017 at 11:47 AM, Fabio Estevam <festevam@gmail.com> wrote:
> >>>> Hi Gary,
> >>>>
> >>>> On Sat, Mar 4, 2017 at 9:33 AM, Fabio Estevam <festevam@gmail.com> wrote:
> >>>>
> >>>>> Not yet, still stuck at the "drmModeGetResources failed" error.
> >>>>
> >>>> I can also get this same error with the new kmscube package from:
> >>>> https://cgit.freedesktop.org/mesa/kmscube/log/
> >>>>
> >>>> # kmscube
> >>>> drmModeGetResources failed: Invalid argument
> >>>> failed to initialize legacy DRM
> >>>>
> >>>> It works if I explicitly pass the /dev/dri device:
> >>>>
> >>>> kmscube -D /dev/dri/card1
> >>>>
> >>>> I think QT5 is trying to access /dev/dri/card0, but it should be using
> >>>> /dev/dri/card1 instead.
> >>>
> >>> Yes, this is the problem.
> >>>
> >>> If I do an ugly hack like this:
> >>>
> >>> --- a/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
> >>> +++ b/src/plugins/platforms/eglfs/deviceintegration/eglfs_kms/qeglfskmsdevice.cpp
> >>> @@ -344,7 +344,7 @@ bool QEglFSKmsDevice::open()
> >>>      Q_ASSERT(m_gbm_device == Q_NULLPTR);
> >>>
> >>>      qCDebug(qLcEglfsKmsDebug) << "Opening device" << m_path;
> >>> -    m_dri_fd = qt_safe_open(m_path.toLocal8Bit().constData(), O_RDWR
> >>> | O_CLOEXEC);
> >>> +    m_dri_fd = qt_safe_open("/dev/dri/card1", O_RDWR | O_CLOEXEC);
> >>>      if (m_dri_fd == -1) {
> >>>          qErrnoWarning("Could not open DRM device %s", qPrintable(m_path));
> >>>          return false;
> >>> --
> >>> 2.7.4
> >>>
> >>> Then the demo is launched. It still do not run very well, but at least
> >>> it starts.
> >>>
> >>> Does anyone have an idea on what would be a proper fix?
> >>
> >> That's strange I didn't have to do that. Worst part is that my demo
> >> image is using Qt5.6.2 (same as your image) and that I checked no
> >> special env variable is set.
> >>
> >> Maybe you can try your kernel on my image, see if that works.
> >
> > I just used rootfs, from the link, and kernel 4.9.13 mainline.
> >
> > Able to see the demo nicely.
> >
> > Order:
> > - kmscube
> > - Boundary devices Tux
> > - jellyfish
> > - ideas in motion
> > - 28 fps (1. Lord of the Rings)
> >
> > So, I'm investigating config options on buildroot will let you know
> > for further update.
> 
> And by the way, did anyone find this issue.
> 
> In file included from
> /workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/egl.h:39:0,
>                  from
> ../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/../../../../../src/platformsupport/eglconvenience/qt_egl_p.h:63,
>                  from
> ../../../../include/QtEglSupport/5.8.0/QtEglSupport/private/qt_egl_p.h:1,
>                  from api/qeglfsglobal_p.h:56,
>                  from api/qeglfsintegration_p.h:54,
>                  from qeglfsmain.cpp:41:
> /workspace/buildroot/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/EGL/eglplatform.h:119:22:
> fatal error: X11/Xlib.h: No such file or directory
>  #include <X11/Xlib.h>
>                       ^
> compilation terminated.
> 
> Look like Qt5.8.0 is unable to build with current tool-chain, 5.6.2 succeeded

Should not happen ;-), mind to share the .config file?

Regards,
Peter

> 
> thanks!

[Buildroot] libqeglfs.so not found on imx6

[Fabio Estevam]

Hi Peter,

On Mon, Mar 6, 2017 at 6:05 PM, Peter Seiderer <ps.report@gmx.net> wrote:

> Should not happen ;-), mind to share the .config file?

I am also able to reproduce this build error. Just shared my defconfig
on a new thread, so that we can discuss about it.

Thanks