Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-67845

Bad Qt Quick application rendering when using QtWayland on i.MX6 SoC with Etnaviv driver

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • P2: Important
    • 5.13.0 Alpha 1
    • 5.10.1
    • QPA: Wayland
    • None
    • Yocto project based Linux distribution using Linux 4.16.1 and Qt 5.10.1 (from meta-qt5 layer) on i.MX6 Quad SoC with Etnaviv graphics stack.
    • 3f05293648fd9b135bbe675d1b2ec873bae299ce (qt/tqtc-qtwayland/5.15.1)

    Description

      I am working on an embedded Linux system based on the NXP i.MX6 Quad SoC and build my Yocto project based distribution using Linux 4.16.1 and Qt 5.10.1 (from meta-qt5 layer). I am using open-source graphics (Etnaviv driver and Mesa 17.1.7), NOT the proprietary Vivante graphics stack provided by NXP.

      I try to render a simple Qt Quick application as a Wayland client on top of the Qt Wayland compositor. The QML-based application (see ExpectedOutput.png) is supposed to show a simple red square inside of a white square (this is what I get on a simple Linux desktop PC build of the same application). However. the Qt Quick application (as seen in QtWayland_on_etnaviv.png) is rendered badly.

      As far as I understand, this is because Qt Wayland compositor currently does not implement the unstable zwp_linux_dmabuf protocol described in this article:
      https://www.pengutronix.de/en/2017-09-28-etnaviv-weston-mainline.html

      I would like this issue to be resolved somehow so that the mainline kernel and open-source graphics stack become usable with the Qt Wayland compositor on the i.MX6 Quad SoC.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              johanhelsing Johan Helsing
              eduardas_meile Eduardas Meile
              Votes:
              5 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes