Summary: | VK_KHR_xlib_surface not enabled by default | ||
---|---|---|---|
Product: | Mesa | Reporter: | Nicolas Koch <nioko1337> |
Component: | Drivers/Vulkan/intel | Assignee: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | bugs.freedesktop.org, jason, nioko1337 |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Nicolas Koch
2016-07-27 12:20:12 UTC
The reason there is no compile flag is because Tue code doesn't yet exist. However, XCB and Xlib can be mixed as seen here: https://www.x.org/wiki/guide/xlib-and-xcb/#index2h2 You should be able to use the xcb version in your Xlib app as long as your Xlib is anywhere close to recent. That's probably how I would implement it inside the driver anyway. If there is a particularly compelling reason to have a separate Xlib implementation I'm open to it but I really don't see one other then slight convenience at the moment. Well, the main reason is that I am using a community driven vulkan wrapper that currently only supports xlib. I cannot use this wrapper, because the extension is not enabled in the driver. I guess I will send them a patch, but nevertheless I think supporting all vulkan extensions (at least the most basic ones like VK_KHR_xlib_surface) should be one of the goals of a feature complete driver. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.