Bring up Samsung proprietary VK driver on proot linux

[mshzhb]

I'm trying to get Samsung's proprietary Vulkan driver (VK UMD) working on Termux-X11 proot linux. I heard that a special patch is needed for Termux-X11 since it differs from standard X11. The Samsung Vulkan driver has native X server & DRI3 support, but it seems like Termux-X11 might require modifications for compatibility.

Does anyone have experience or guidance on patching Termux-X11 for this setup? Any resources or help would be greatly appreciated. (my email: [email protected])

Thanks in advance!

[twaik]

Currently it is possible to use proprietary drivers with termux-x11 with xMeM's vulkan-wsi-layer mesa-vulkan-icd-wrapper. I do not add regular DRM/KMS to termux x11 because there is no public Android API for that and even if I will use some non-public APIs it will break rendering on other devices.

[mshzhb]

Thanks a lot for the immediate response! I'm intending to bring it up on proot linux. Probably termux + glibc environment later. I'm new to this environment.

Currently, the vulkaninfo is working. However, vkcube fails in window creation.

[twaik]

Start termux-x11 with -disable-dri3 flag.

[mshzhb]

Hi @twaik, is it possible to use wayland in termux instead of x server?

[mshzhb]

offscreen rendering and compute are working now

[twaik]

With labwc (from PR) or weston.

[mshzhb]

offscreen rendering is working.
However, having some issues with xcb_dri3_open_reply
Here is the error code: DRI3 related

error_code = 0x8 (BadMatch)
major_code = 0x93 (dri3 related)
minor_code = 0x1

[twaik]

Because termux-x11's dri3 is not a full implementation your driver expects. You can send or ahardwarebuffer or some mmappable fd.

[mshzhb]

Thanks a lot sir! That's the answer I'm looking for! Since turnip can work on termux-x11, there should be a way for samsung(AMD) driver to work

[mshzhb]

Do you have any more information on this topic? Who makes turnip working on termux?

[twaik]

https://github.com/termux/termux-packages/blob/master/packages/mesa-vulkan-icd-freedreno-dri3/wsi-termux-x11.patch

[mshzhb]

Hi @twaik & @xMeM,

For on-screen rendering, our driver is already functional on proot Linux with CPU blit, but I’m currently working on enabling DRI3. Could you clarify whether, for Turnip to work with Termux-X11, I only need to apply wsi-termux-x11.patch, or is the tu_kgsl_export_dmabuf.patch required as well?

Currently, xcb_dri3_pixmap_from_buffers_checked(..., 1274, &fd) is returning error_code = 11.

Thanks,
Tong

[xMeM]

Requires driver support for EGL_EXT_image_dma_buf_import.

[mshzhb]

Thanks a lot @twaik & @xMeM. DRI3 is working now. The last task I need to do is fixing xshmfence according to [wsi-termux-x11.patch], isn't it?

Btw, in this setup can I use optimal tiling for the framebuffer? Currently only linear works.

Currently I'm unclear why this turnip branch (https://gitlab.freedesktop.org/Pipetto-crypto/mesa/-/commits/winlator_wsi-termux-x11?search=termux) can work while still keep the xshmfence

[xMeM]

termux-x11 uses pixman (cpu based acceleration) which can only handle linear tiling. When the framebuffer uses optimal tiling, it needs to be copied to a linear buffer.

This branch (https://gitlab.freedesktop.org/Pipetto-crypto/mesa/-/commits/winlator_wsi-termux-x11?search=termux) use xcb_sync_fence instead of xshmfence, it still removes xshmfence.

[twaik]

XCB fence is a valid option even if it will be a bit slower.

[mshzhb]

Thanks for the guidance! With xcb_sync_fence, our umd is fully working now!