[Mesa-dev] Question about EGL_KHR_partial_update implementation

Qiang Yu yuq825 at gmail.com
Thu Jun 28 09:55:26 UTC 2018

Hi Harish,

I want to implement EGL_KHR_partial_update for lima mesa driver and find you
worked on Android/Wayland support for it:

So I have some question about it:
your implementation seems to depend on platform (Android, wayland) support,
for example call native_window_set_surface_damage() in Android implementation.
What's the purpose of it, tell the Android SurfaceFlinger to redraw the damage
region? And is this damage region the "surface damage" or "buffer
damage" metioned
in the EGL_KHR_partial_update?

To my understand this extension should only depend on the driver support instead
of platform support while the EGL_KHR_swap_buffers_with_damage is the opposite:

For lima implementation, I want to use the damage region (buffer
damage) provided
by EGL_KHR_partial_update to skip rendering of un-damaged region when
eglSwapBuffersXXX. And tell damage region (surface damage) to compositor should
be left to eglSwapBuffersWithDamageKHR provided by


More information about the mesa-dev mailing list