-
-
Notifications
You must be signed in to change notification settings - Fork 160
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
X11 WSI support for android targets? #435
Comments
Interestingly, this would cause the framebuffer to be read by the AHardwareBuffer and sending it to x11, correct? |
Not exactly. It will cause rendering directly to AHardwareBuffer, which will be read by X server during rendering the root window. |
I hope the implementation is soon |
You can try opening another poll to try to get an answer |
@ptitSeb please add framebuffer and x11 support when using gl4es on termux or termux-x11 platforms in case of android definitions without NOX11 |
And how do I do that? |
You can create wrap all EGL calls and emulate X11 surface. Try to read this. https://github.com/tareksander/termux-gfx-wrapper/tree/main/src/egl |
I don't speak English, the shit on Google Translate fails, but I wish that when NOX11 is not used, x11 support would be enabled both in buffers too, there are many projects now that use x11+box64 in Mali gpus, this could be something good |
Hi. GL4ES can be used on Android devices but there is no X11 support. Can you please port mesa's X11 WSI code (this + this)? Or maybe mesa's vulkan X11 WSI code (this)? You can use AHardwareBuffer API for EGLImage and set it as framebuffer/renderbuffer and attach AHardwareBuffer's udmabuf fd to X server with simple
xcb_shm_attach_fd
call and then draw it withxcb_shm_put_image
call.Thank you.
The text was updated successfully, but these errors were encountered: