From 48becd0d71aa2fb1ca5b31c77b66997fe1f77737 Mon Sep 17 00:00:00 2001 From: Wujian Sun Date: Wed, 1 Nov 2023 18:19:23 +0800 Subject: [PATCH 1/7] Fixed chromium flicker with g2d-renderer chromium V89 reland linux_explicit_synchronization_protocol for in-fence feature caused the flicker. The rootcasue is that weston can not acquire fence fd. A workaround no checking supports_acquire_fence supported. Upstream-Status: Inappropriate [i.MX specific] Signed-off-by: Wujian Sun --- ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc b/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc index acb4a60ba01ea..e93533cecaeb7 100644 --- a/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc +++ b/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc @@ -208,8 +208,7 @@ void GbmSurfacelessWayland::Present(SwapCompletionCallback completion_callback, unsubmitted_frames_.back()->configs.reserve(frame->configs.size()); // If Wayland server supports linux_explicit_synchronization_protocol, fences // should be shipped with buffers. Otherwise, we will wait for fences. - if (buffer_manager_->supports_acquire_fence() || !use_egl_fence_sync_ || - !frame->schedule_planes_succeeded) { + if (!use_egl_fence_sync_ || !frame->schedule_planes_succeeded) { frame->ready = true; MaybeSubmitFrames(); return; -- 2.34.1