Bug 97096 - VK_KHR_xlib_surface not enabled by default
Summary: VK_KHR_xlib_surface not enabled by default
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/intel (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-07-27 12:20 UTC by Nicolas Koch
Modified: 2017-01-11 20:33 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Nicolas Koch 2016-07-27 12:20:12 UTC
The vulkan extension VK_KHR_xlib_surface is not enabled, even though I'm compiling on a X11 platform. XCB on the other hand is enabled.

Unfortunately, I cannot use xcb and do not know how to compile the driver with VK_KHR_xlib_surface enabled.

I originally submitted this bug in the archlinux bugtracker, but got send here because they said it's an upstream choice to not enable xlib support.

The original bug can be found here https://bugs.archlinux.org/task/50160 (and adds some context about configure flags that I don't know much about, so please also take a look at that bug report)
Comment 1 Jason Ekstrand 2016-07-27 17:01:58 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.
Comment 2 Nicolas Koch 2016-07-28 01:47:24 UTC
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.