Skip to content
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

Add zwp_linux_dmabuf_v1 support to Wayland WSI #96

Closed
i509VCB opened this issue Jan 10, 2024 · 4 comments
Closed

Add zwp_linux_dmabuf_v1 support to Wayland WSI #96

i509VCB opened this issue Jan 10, 2024 · 4 comments
Labels

Comments

@i509VCB
Copy link

i509VCB commented Jan 10, 2024

I noticed that the Wayland WSI currently uses the old wl_drm. Most compositor implementations better support the newer zwp_linux_dmabuf_v1 protocol. wl_drm might not necessarily be available if the compositor uses Vulkan for rendering.

@JakeMerdichAMD
Copy link
Contributor

I've added this new wayland protocol to our backlog (it has other benefits like improved startup time too). The crash you linked does not quite seem like a bug on our end, though. Instead of using modifiers, the wl_drm protocol uses vendor-specific metadata paths just like X11 and only uses the format for the vendor-neutral part of the format (eg RGBA8888 or RGB565).

@i509VCB
Copy link
Author

i509VCB commented Jan 11, 2024

Yeah the wl_drm issue is one with smithay and cosmic, but the newer protocol is appreciated.

@jinjianrong
Copy link
Member

Tracked with SWDEV-440638 internally

@jinjianrong
Copy link
Member

Done in 2024.Q4.1 release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants