mirror of
https://gitlab.freedesktop.org/mesa/mesa.git
synced 2026-05-21 08:58:10 +02:00
f2e0f5c3c4
The dri options are optional. When the dri options are not provided the WSI will not use adaptive sync. FWIW I think for xf86-video-amdgpu this still requires an X11 config option, so only people who opt in can get possible regressions from this. So then the remaining question is: why do this in the WSI? It has been suggested in another MR that the application sets this. However, I disagree with that as I don't think we'll ever get a reasonable set of applications setting it. The next questions is whether this can be a layer. It definitely can be as implemented now. However, I think this generally fits well with the function of the WSI. Furthemore, for e.g. the DISPLAY WSI this is much harder to do in a layer. Of course, most of the WSI could almost be a layer, but I think this still fits best in the WSI. Acked-by: Jason Ekstrand <jason@jlekstrand.net> |
||
|---|---|---|
| .. | ||
| .clang-format | ||
| meson.build | ||
| TODO | ||
| tu_android.c | ||
| tu_cmd_buffer.c | ||
| tu_cs.c | ||
| tu_cs.h | ||
| tu_descriptor_set.c | ||
| tu_descriptor_set.h | ||
| tu_device.c | ||
| tu_drm.c | ||
| tu_entrypoints_gen.py | ||
| tu_extensions.py | ||
| tu_fence.c | ||
| tu_formats.c | ||
| tu_icd.py | ||
| tu_image.c | ||
| tu_meta_blit.c | ||
| tu_meta_buffer.c | ||
| tu_meta_clear.c | ||
| tu_meta_copy.c | ||
| tu_meta_resolve.c | ||
| tu_pass.c | ||
| tu_pipeline.c | ||
| tu_pipeline_cache.c | ||
| tu_private.h | ||
| tu_query.c | ||
| tu_shader.c | ||
| tu_util.c | ||
| tu_util.h | ||
| tu_wsi.c | ||
| tu_wsi_wayland.c | ||
| vk_format.h | ||
| vk_format_layout.csv | ||
| vk_format_parse.py | ||
| vk_format_table.py | ||