Robert Mader aaae07f9dd onscreen/native: Mark GPU rendering duration as valid if supported ... Since commit e30eb78891 `ClutterFrameClock` assumes that a valid CPU time implies timestamp query support, which is also checked in `cogl_onscreen_egl_swap_buffers_with_damage()`. Unconditionally setting the CPU time on direct scanout meant that the compositing path would be stuck on the last (direct scanout optimized) result on GL implementations without timestamp query support since. be0aa2976e (clutter/frame-clock: Avoid rapidly toggling dynamic max render time) Fix that by explicitly marking the gpu rendering duration as valid when querying the GPU timestamps is supported and check for it ClutterFrameClock. Fixes: 56580ea7c9 ("backends/native: Assume zero rendering time for direct scanout buffers") Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3655>		2024-03-13 16:37:16 +01:00
..
clutter	onscreen/native: Mark GPU rendering duration as valid if supported	2024-03-13 16:37:16 +01:00
meson.build	clutter: Explicitly depend on cairo	2024-01-27 10:03:15 +00:00