diff options
author | Otavio Salvador <otavio@ossystems.com.br> | 2023-01-10 08:59:03 -0300 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-01-10 08:59:03 -0300 |
commit | 1c7f17f6063d0b747d94a17059b176f3ebdb3e3e (patch) | |
tree | 5da96ff55339ea98501a9e1f7544a243b20e9983 /dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland/0001-Fixed-chromium-flicker-with-g2d-renderer.patch | |
parent | bd8ff87bf68f52b3933c5d1e9f83c610f18a963d (diff) | |
parent | 481b7f0468b3f5928f8f0fc6aa21e4836fb3f3c5 (diff) | |
download | meta-freescale-1c7f17f6063d0b747d94a17059b176f3ebdb3e3e.tar.gz |
Merge pull request #1380 from Freescale/backport-1375-to-kirkstone
[Backport kirkstone] chromium-ozone-wayland: add bbappend and patches as per NXP 5.15.71_2…
Diffstat (limited to 'dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland/0001-Fixed-chromium-flicker-with-g2d-renderer.patch')
-rw-r--r-- | dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland/0001-Fixed-chromium-flicker-with-g2d-renderer.patch | 33 |
1 files changed, 33 insertions, 0 deletions
diff --git a/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland/0001-Fixed-chromium-flicker-with-g2d-renderer.patch b/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland/0001-Fixed-chromium-flicker-with-g2d-renderer.patch new file mode 100644 index 00000000..3aa41ecf --- /dev/null +++ b/dynamic-layers/chromium-browser-layer/recipes-browser/chromium/chromium-ozone-wayland/0001-Fixed-chromium-flicker-with-g2d-renderer.patch | |||
@@ -0,0 +1,33 @@ | |||
1 | From 1c7fd64b69feb0ea14047ce1ed68138ccf33687e Mon Sep 17 00:00:00 2001 | ||
2 | From: Wujian sun <wujian.sun_1@nxp.com> | ||
3 | Date: Mon, 5 Jul 2021 10:28:44 +0800 | ||
4 | Subject: [PATCH] Fixed chromium flicker with g2d-renderer | ||
5 | |||
6 | chromium V89 reland linux_explicit_synchronization_protocol for | ||
7 | in-fence feature caused the flicker. | ||
8 | The rootcasue is that weston can not acquire fence fd. | ||
9 | A workaround no checking supports_acquire_fence supported. | ||
10 | |||
11 | Upstream-Status: Inappropriate [i.MX specific] | ||
12 | Signed-off-by: Wujian sun <wujian.sun_1@nxp.com> | ||
13 | --- | ||
14 | ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc | 3 +-- | ||
15 | 1 file changed, 1 insertion(+), 2 deletions(-) | ||
16 | |||
17 | diff --git a/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc b/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc | ||
18 | index e7d3e7268a08..83c57fd65d72 100644 | ||
19 | --- a/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc | ||
20 | +++ b/ui/ozone/platform/wayland/gpu/gbm_surfaceless_wayland.cc | ||
21 | @@ -112,8 +112,7 @@ void GbmSurfacelessWayland::SwapBuffersAsync( | ||
22 | |||
23 | // If Wayland server supports linux_explicit_synchronization_protocol, fences | ||
24 | // should be shipped with buffers. Otherwise, we will wait for fences. | ||
25 | - if (buffer_manager_->supports_acquire_fence() || !use_egl_fence_sync_ || | ||
26 | - !frame->schedule_planes_succeeded) { | ||
27 | + if (!use_egl_fence_sync_ || !frame->schedule_planes_succeeded) { | ||
28 | frame->ready = true; | ||
29 | MaybeSubmitFrames(); | ||
30 | return; | ||
31 | -- | ||
32 | 2.17.1 | ||
33 | |||