Open hansm629 opened 2 days ago
IIRC chromium
ships its own vulkan loader, so I don't know how to make it work...
@licy183
Is it possible to implement OpenGL & OpenGL ES
in X11
by combining mesa-vulkan-icd-wrapper
with Google ANGLE
instead of using a virgl
environment?
Since mesa-vulkan-icd-wrapper
allows Termux
to access the Android host Vulkan driver
and supports X11 WSI
, this approach could offer significant performance improvements and better compatibility compared to the existing angle-android + virglrenderer-android
setup.
This might also serve as an alternative solution for implementing OpenGL & OpenGL ES
on Vulkan drivers
that lack compatibility with Zink
.
Could you review this?
Problem description
I am currently testing
mesa-vulkan-icd-wrapper
, which allows the use of theAndroid host Vulkan driver
inTermux
.Most SoC GPUs showed poor compatibility with
mesa zink
, and theChromium browser
either didn’t launch or GPU acceleration didn’t work.To use
ANGLE
with theVulkan backend
, I tried launching theChromium browser
as follows, but it didn’t start.What steps will reproduce the bug?
When checking with the
vulkaninfo
command, even though most extensions required forX11
are supported throughmesa-vulkan-icd-wrapper
, an error shows thatVK_KHR_surface
andVK_KHR_xcb_surface
are not supported.vulkaninfo
``` ~$ vulkaninfo ========== VULKANINFO ========== Vulkan Instance Version: 1.3.301 Instance Extensions: count = 24 =============================== VK_EXT_acquire_drm_display : extension revision 1 VK_EXT_debug_report : extension revision 10 VK_EXT_debug_utils : extension revision 2 VK_EXT_direct_mode_display : extension revision 1 VK_EXT_display_surface_counter : extension revision 1 VK_EXT_headless_surface : extension revision 1 VK_EXT_surface_maintenance1 : extension revision 1 VK_EXT_swapchain_colorspace : extension revision 4 VK_GOOGLE_surfaceless_query : extension revision 2 VK_KHR_device_group_creation : extension revision 1 VK_KHR_display : extension revision 23 VK_KHR_external_fence_capabilities : extension revision 1 VK_KHR_external_memory_capabilities : extension revision 1 VK_KHR_external_semaphore_capabilities : extension revision 1 VK_KHR_get_display_properties2 : extension revision 1 VK_KHR_get_physical_device_properties2 : extension revision 2 VK_KHR_get_surface_capabilities2 : extension revision 1 VK_KHR_portability_enumeration : extension revision 1 VK_KHR_surface : extension revision 25 VK_KHR_surface_protected_capabilities : extension revision 1 VK_KHR_wayland_surface : extension revision 6 VK_KHR_xcb_surface : extension revision 6 VK_KHR_xlib_surface : extension revision 6 VK_LUNARG_direct_driver_loading : extension revision 1 Layers: ======= Presentable Surfaces: ===================== GPU id : 0 (Samsung Xclipse 940): Surface types: count = 2 VK_KHR_xcb_surface VK_KHR_xlib_surface Formats: count = 2 SurfaceFormat[0]: format = FORMAT_B8G8R8A8_UNORM colorSpace = COLOR_SPACE_SRGB_NONLINEAR_KHR SurfaceFormat[1]: format = FORMAT_B8G8R8A8_SRGB colorSpace = COLOR_SPACE_SRGB_NONLINEAR_KHR ```
How can I implement
OpenGL ES 3.2
acceleration in the Chromium browser using "ANGLE: Vulkan Back-end
"?What is the expected behavior?
No response
System information
termux-info: