AW: wayland: wrong tiling with wl_drm on Vivante GC2000

[Christian Gudrian]

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 got some numbers 
confused).

With the compositor itself doing the FPS computation both protocols (wl_drm and 
dmabuf) show similar FPS numbers and low CPU usage.

Christian

AW: wayland: wrong tiling with wl_drm on Vivante GC2000

[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 tiling problem. However 
the CPU usage is much higher and the FPS drops from 60 to 30 (I can see a 
similar behavior with Weston).

Christian