This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3354: AM3354: OpenGL/QT font rendering problem - corrupt glyphs - solution committed?

Part Number: AM3354

Hi there,

In the other (locked) thread "AM3354: OpenGL/QT font rendering problem - corrupt glyphs"

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/877088/am3354-opengl-qt-font-rendering-problem---corrupt-glyphs

there are attached ddk-um binaries for yocto dunfell/thud , which also work for us for zeus

Have the binaries of the other thread been committed to git://git.ti.com/graphics/omap5-sgx-ddk-um-linux.git ?

Have these been integrated in meta-ti ? 

if so what is the commit hash or the associated tag of either of those? (i have been md5summing all revisions but there is no identical match)

thanks.

  • i a guessing meta-ti  zeus branch has not updated the commit hash of ti-sgx-ddk-um_1.17.4948957.bb:

    it is @ ce7b96b88.., updating it to 551665.. should do the trick

    can someone confirm the 551665.. commit has in omap5-sgx-ddk-um-linux.git does have the fix in there?

    (sidenote: for people that have issues compiling the latest meta-ti zeus branch, ti-sgx-ddk-km in this branch is for kernel 5.4 and not 4.19 select an older commit 2a777b8fb...)

  • super thanks for the confirm,

    so in meta-ti for ti-sgx-ddk-um_1.17.4948957.bb updating SRCREV to 551665 would pickup this commit (that includes your 7519eda..)

    however with this commit, qt (5.14.0 and 5.15.2) do not recognize the eglfs device anymore, (and with the forumthread attached drivers it works normally) (with kernel module @ 2a777b8)

    is the combo um + km correct and are these drivers verified on the eglfs path?  (we are running a 4.19 kernel)

  • here is the application output

    command:
    QT_QPA_EGLFS_DEBUG=1 \
    QT_LOGGING_RULES="qt.qpa.egldeviceintegration=true;qt.qpa.eglfs.kms=true" \
    QT_QPA_PLATFORM=eglfs \
    QT_QPA_EGLFS_INTEGRATION=eglfs_kms_egldevice \
    QT_QPA_EGLFS_ALWAYS_SET_MODE=1 \
    QT_QPA_EGLFS_KMS_CONFIG=/banana-config \
    ./out-qt-application
    
    output:
    QML debugging is enabled. Only use this in a safe environment.
    QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
    qt.qpa.egldeviceintegration: EGL device integration plugin keys: ("eglfs_emu", "eglfs_kms_egldevice", "eglfs_kms")
    qt.qpa.egldeviceintegration: EGL device integration plugin keys (sorted): ("eglfs_kms", "eglfs_emu", "eglfs_kms_egldevice")
    qt.qpa.egldeviceintegration: Trying to load device EGL integration "eglfs_kms"
    qt.qpa.eglfs.kms: Loading KMS setup from "/banana-config"
    qt.qpa.eglfs.kms: Requested configuration (some settings may be ignored):
            headless: false 
            hwcursor: false 
            pbuffers: true 
            separateScreens: false 
            virtualDesktopLayout: 0 
            outputs: QMap(("DSI-1", QMap(("mode", QVariant(QString, "800x1280"))("name", QVariant(QString, "DSI-1")))))
    qt.qpa.eglfs.kms: New DRM/KMS via GBM integration created
    qt.qpa.egldeviceintegration: Using EGL device integration "eglfs_kms"
    qt.qpa.eglfs.kms: platformInit: Opening DRM device
    qt.qpa.eglfs.kms: GBM: Using DRM device "/dev/dri/card0" specified in config file
    qt.qpa.eglfs.kms: Using backend-provided DRM device /dev/dri/card0
    qt.qpa.eglfs.kms: Creating GBM device for file descriptor 4 obtained from "/dev/dri/card0"
    qt.qpa.eglfs.kms: Initalizing event reader for device 0x5d9930 fd 4
    qt.qpa.eglfs.kms: Querying EGLDisplay
    Could not initialize egl display
    Aborted
    

  • seems the *WS* libs are now gone and mesa has been introduced,

    does somebody perhaps have a hint to configure QT to support this new mesa thingy?

    this is how we have configured it atm with the previous drivers:

    EGLFS details:
        EGLFS OpenWFD ........................ no
        EGLFS i.Mx6 .......................... no
        EGLFS i.Mx6 Wayland .................. no
        EGLFS RCAR ........................... no
        EGLFS EGLDevice ...................... yes
        EGLFS GBM ............................ yes
        EGLFS VSP2 ........................... no
        EGLFS Mali ........................... no
        EGLFS Raspberry Pi ................... no
        EGLFS X11 ............................ no
    

  • Hello,

    Could you please try to set the following variable "export QT_QPA_EGLFS_INTEGRATION=eglfs_kms"?

    Regards,
    Krunal

  • in /etc/powervr.ini we still have this:

    WindowSystem=libpvrDRMWSEGL.so

    but the library does not exist in the new version.

    setting QT_QPA_EGLFS_INTEGRATION=eglfs_kms does not change the result.

  • Hello,

    1. Please refer to the following document: http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Foundational_Components/Graphics/Migration_From_Prior_Releases.html#from-processor-sdk-6-1-to-6-2-for-am3-4-5-6

    2. As an experiment, I would recommend you to try the default file-system that comes with TI SDK. I am not able to replicate the issue on my setup. If default SDK file system works, we can try comparing your Yocto recipe with TI recipe.

    Regards,
    Krunal