topic Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch. in i.MX Processors

EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

pavansingpatil — Tue, 16 Jan 2018 06:24:02 GMT

Hi,

We updated our yocto version to krogoth branch, we are using qt-5.6 + viv eglfs backend. something i noticed is ibqeglfs-viv-integration.so is missing from plugin directory and kms plugin getting compiled.

how to enabled this in yocto conf? any suggestion?

have enabled this in conf/local.conf

DISTRO_FEATURES_remove = "x11 wayland"

PACKAGECONFIG_append_pn-qtbase = "eglfs gl gles2"

Thanks.

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

igorpadykov — Tue, 16 Jan 2018 09:17:29 GMT

Hi pavansingpatil

what bsp used in the case, one can try with nxp releases using

sect.5.2 Choosing a Freescale Yocto project image attached Yocto Guide

and with demo images found on link

https://www.nxp.com/support/developer-resources/run-time-software/i.mx-developer-resources/i.mx-6series-i.mx-7series-software-and-development-tool-resources:IMX_SW

for third party releases one can look on

[meta-freescale] imx6dlsabresd + qt5 + gstreamer

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

pavansingpatil — Tue, 16 Jan 2018 09:30:21 GMT

Hi igor,

Thanks for quick reply.

we have imx6solo custom board and using Freescale community BSP. everything was working fine with jethro branch while updating to morty we see issue this eglfs issue.

we can't use demo image since we have been working on custom hardware based on imx6.

ls usr/lib/qt5/plugins/egldeviceintegrations/

libqeglfs-kms-egldevice-integration.so

Thanks.

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

igorpadykov — Tue, 16 Jan 2018 12:03:01 GMT

Hi pavansingpatil

community releases may be supported on meta-fsl-arm mailing list:
https://lists.yoctoproject.org/listinfo/meta-freescale

Best regards
igor

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

pavansingpatil — Tue, 16 Jan 2018 12:19:47 GMT

Hi igor,

GitHub - Freescale/meta-freescale: Layer containing NXP hardware support metadata

I am using the layers from freescale github repos.

didn't get,you mean i should ask this question there?

Thanks.

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

igorpadykov — Tue, 16 Jan 2018 14:09:38 GMT

Hi pavansingpatil

these are community releases supported on meta-fsl-arm mailing list:
https://lists.yoctoproject.org/listinfo/meta-freescale

nxp official bsp is on

linux-imx.git - i.MX Linux Kernel

description is on

i.MX Software|NXP

difference between community bsp and NXP(Freescale) offical bsp

difference between Yocto Community BSP and Freescale BSP Release

support policy is described in sect.Machine Maintainers :

FSL Community BSP Release Notes 2.2 documentation

every new board must have someone assigned as maintainer. This ensures, in

long term, all boards with a maintainer assigned. Current orphan boards are not going to

be removed unless it causes maintenance problem and the fix is not straightforward.

The maintainer duties:

The one with casting vote when a deadlock is faced.
Responsible to keep that machine working (that means, booting and with some stability) Keep kernel, u-boot updated/tested/working.
Keep release notes updated
Keep test cycle updated
Keep the most usual images building and booting"

When a build error is detected, the maintainer will “fix” it. For those maintainers with kernel

control (meta-freescale-3rdparty), it is expected that they properly fix the kernel issue (when it’s a kernel issue). "

Best regards
igor

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

pavansingpatil — Mon, 29 Jan 2018 12:44:32 GMT

in qt-5.6 configuration eglfs_viv option is missing.

Build options:

some useful logs:
Configuration .......... accessibility audio-backend c++11 c++14 c++1z clock-gettime clock-monotonic compile_examples concurrent cross_compile dbus dbus-linked egl eglfs eglfs_egldevice evdev eventfd

eglfs_egldevice should get replace with eglfs_viv.

QPA backends:
DirectFB ............. no
EGLFS ................ yes
EGLFS i.MX6 ........ no
EGLFS i.MX6 Wayland. no
EGLFS EGLDevice .... yes
EGLFS GBM .......... no
EGLFS Mali ......... no
EGLFS Raspberry Pi . no
EGLFS X11 .......... no
LinuxFB .............. no
Mir client............ no
XCB .................. no

Can someone please guide to enable viavante backend in meta-freescale layer? which is latest yocto nxp official release?

Thanks in advance.

Re: EGL_EXT_device_base missing Aborted (core dumped)? libqeglfs-viv-integration.so is missing after updated to yocto morty branch.

pavansingpatil — Mon, 29 Jan 2018 13:30:16 GMT

I have added below lines to my qtbase_git.bbappend and it's get append to qmake.conf file in mkspec

cat >> ${S}/mkspecs/linux-oe-g++/qmake.conf <<EOF
IMX6_CFLAGS = -DLINUX=1 -DEGL_API_FB=1
EGLFS_DEVICE_INTEGRATION = eglfs_viv
QMAKE_LIBS_EGL += -lEGL
QMAKE_LIBS_OPENGL_ES2 += -lGLESv2 -lEGL
QMAKE_LIBS_OPENVG += -lOpenVG -lEGL
QMAKE_CFLAGS_RELEASE += \$\$IMX6_CFLAGS
QMAKE_CXXFLAGS_RELEASE += \$\$IMX6_CFLAGS
QMAKE_CFLAGS_DEBUG += \$\$IMX6_CFLAGS
QMAKE_CXXFLAGS_DEBUG += \$\$IMX6_CFLAGS

load(qt_config)

but doesn't make any difference in configuration. Thanks.