brl/mutter
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

onscreen/native: Don't release the dumb buffers on successful zero-copy

Browse Source 
Because a zero-copy import might fail later for driver or resource reasons.
So we may still need the dumb buffers as a fallback.

Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3606
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3928>
This commit is contained in:
Daniel van Vugt 2024-08-07 15:30:37 +08:00 committed by Marge Bot
parent ced0d34142
commit 31e280c147
1 changed files with 0 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/backends/native/meta-onscreen-native.c
View File

@ -822,12 +822,6 @@ import_shared_framebuffer (CoglOnscreen *onscreen,
if (secondary_gpu_state->import_status == if (secondary_gpu_state->import_status ==
META_SHARED_FRAMEBUFFER_IMPORT_STATUS_NONE) META_SHARED_FRAMEBUFFER_IMPORT_STATUS_NONE)
{ {
/*
* Clean up the cpu-copy part of
* init_secondary_gpu_state_cpu_copy_mode ()
*/
secondary_gpu_release_dumb (secondary_gpu_state);
meta_topic (META_DEBUG_KMS, meta_topic (META_DEBUG_KMS,
"Using zero-copy for %s succeeded once.", "Using zero-copy for %s succeeded once.",
meta_render_device_get_name (render_device)); meta_render_device_get_name (render_device));