Chromium seems to use EGL_CHROMIUM_sync_control on Intel, but proprietary Nvidia doesn't support it (bug 1640147 comment 2): https://gitlab.freedesktop.org/mesa/mesa/-/commit/c524f3ef9155caba6cd4f9fc72485426b1da76fd > Chromium defined a new GL extension (that isn't registered with Khronos). > We need to add an EGL extension for it, so we can migrate ChromeOS on Intel systems to use EGL instead of GLX. https://source.chromium.org/chromium/chromium/src/+/master:ui/gl/gl_surface_egl.cc;l=222;drc=912769f6ef3aaffd86632c6268ae311559ffebbe https://source.chromium.org/chromium/chromium/src/+/master:ui/gl/EGL/eglextchromium.h;l=16;drc=5cddfb828ddd82fc741549d5ee44cd9b94bd97f5 See especially: https://gitlab.freedesktop.org/mesa/mesa/-/issues/2930 ----- https://github.com/freedesktop/mesa-demos/blob/master/src/egl/opengl/eglinfo.c KDE, X11, Debian Testing, Mesa 20.0.7, Intel Iris Graphics 6100 (BDW GT3): > X11 platform: > EGL API version: 1.5 > EGL vendor string: Mesa Project > EGL version string: 1.5 > EGL client APIs: OpenGL OpenGL_ES > EGL extensions string: > EGL_ANDROID_blob_cache EGL_ANDROID_native_fence_sync > EGL_CHROMIUM_sync_control EGL_EXT_buffer_age > EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import > EGL_EXT_image_dma_buf_import_modifiers EGL_IMG_context_priority > EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context > EGL_KHR_create_context_no_error EGL_KHR_fence_sync > EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace > EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image > EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image > EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap > EGL_KHR_no_config_context EGL_KHR_reusable_sync > EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float > EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image > EGL_MESA_image_dma_buf_export EGL_MESA_query_driver > EGL_NOK_texture_from_pixmap EGL_WL_bind_wayland_display
Bug 1640779 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Chromium seems to use EGL_CHROMIUM_sync_control on Mesa, but proprietary Nvidia doesn't support it (bug 1640147 comment 2): https://gitlab.freedesktop.org/mesa/mesa/-/commit/c524f3ef9155caba6cd4f9fc72485426b1da76fd > Chromium defined a new GL extension (that isn't registered with Khronos). > We need to add an EGL extension for it, so we can migrate ChromeOS on Intel systems to use EGL instead of GLX. https://source.chromium.org/chromium/chromium/src/+/master:ui/gl/gl_surface_egl.cc;l=222;drc=912769f6ef3aaffd86632c6268ae311559ffebbe https://source.chromium.org/chromium/chromium/src/+/master:ui/gl/EGL/eglextchromium.h;l=16;drc=5cddfb828ddd82fc741549d5ee44cd9b94bd97f5 See especially: https://gitlab.freedesktop.org/mesa/mesa/-/issues/2930 ----- https://github.com/freedesktop/mesa-demos/blob/master/src/egl/opengl/eglinfo.c KDE, X11, Debian Testing, Mesa 20.0.7, Intel Iris Graphics 6100 (BDW GT3): > X11 platform: > EGL API version: 1.5 > EGL vendor string: Mesa Project > EGL version string: 1.5 > EGL client APIs: OpenGL OpenGL_ES > EGL extensions string: > EGL_ANDROID_blob_cache EGL_ANDROID_native_fence_sync > EGL_CHROMIUM_sync_control EGL_EXT_buffer_age > EGL_EXT_create_context_robustness EGL_EXT_image_dma_buf_import > EGL_EXT_image_dma_buf_import_modifiers EGL_IMG_context_priority > EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context > EGL_KHR_create_context_no_error EGL_KHR_fence_sync > EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace > EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image > EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image > EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap > EGL_KHR_no_config_context EGL_KHR_reusable_sync > EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float > EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image > EGL_MESA_image_dma_buf_export EGL_MESA_query_driver > EGL_NOK_texture_from_pixmap EGL_WL_bind_wayland_display