Hi, Lucas!
Thanks for the explanation. That fits the mental model I've built up.
As it turned out it was the Wayland client computing and displaying the FPS
counter which reduced the FPS in the first place. Contrary to what I initially
said the FPS reduction was also present using wl_drm (I
Hi Christian,
Am Donnerstag, dem 30.03.2023 um 19:54 + schrieb Christian Gudrian:
> Hi, Daniel!
>
> Thanks for your reply.
>
> > You need to force QtWayland to use the wp-linux-dmabuf-v1 platform
> > integration for the compositor.
>
> Yes. I've did that before and that indeed solves the
Hi, Daniel!
Thanks for your reply.
> You need to force QtWayland to use the wp-linux-dmabuf-v1 platform
> integration for the compositor.
Yes. I've did that before and that indeed solves the tiling problem. However
the CPU usage is much higher and the FPS drops from 60 to 30 (I can see a
Hi Christian,
On Thu, 30 Mar 2023 at 20:15, Christian Gudrian wrote:
> We're running a custom Wayland compositor based on Qt Wayland on an i.MX6
> Quad system with a Vivante GC2000 GPU using the Mesa Gallium driver. While
> the compositor itself displays correctly, client buffers are displayed
Hello!
We're running a custom Wayland compositor based on Qt Wayland on an i.MX6 Quad
system with a Vivante GC2000 GPU using the Mesa Gallium driver. While the
compositor itself displays correctly, client buffers are displayed with wrong
tiling.
So far I've found out, that the client's
