Lines Matching refs:Vulkan

38     This extension interacts with Vulkan 1.0 and requires the OpenGL
39     implementation to expose an implementation of Vulkan 1.0.
45     the contents of a two-dimensional Vulkan VkImage.  Callers specify a
46     Vulkan VkImage handle, an optional OpenGL sampler object, window
57     In order to synchronize between Vulkan and OpenGL there are three other
59     SignalVkFenceNV().  These allow OpenGL to wait for Vulkan to complete work
60     and also Vulkan to wait for OpenGL to complete work.  Together OpenGL
61     and Vulkan can synchronize on the server without application
65     context to query the Vulkan entry points directly and avoid having to
66     load them through the typical Vulkan loader.
87     The Vulkan base entry point type from which all Vulkan functions pointers
103     1.3.X Vulkan
105     Vulkan is a royalty-free, cross-platform explicit API for full-function
109     OpenGL can interoperate directly with Vulkan to take advantage of Vulkan's
113     An OpenGL application can use the following function to query the Vulkan
118     <name> is the name of the Vulkan function, for example "vkCreateInstance"
119     and the return is a point to the Vulkan function address.  This allows
120     OpenGL applications that need to interoperate with Vulkan to query the 
121     entry points directly and bypass the typical Vulkan loader.  The OpenGL
122     implementation provides access to the Vulkan implementation through this
125     The specification and more information about Vulkan can be found at
133     4.1.X Synchronization between OpenGL and Vulkan
139     causes the GL server to block until the Vulkan VkSemaphore <vkSemaphore>
141     until the semaphore is signaled.  <vkSemaphore> must be a valid Vulkan
148     causes the GL server to signal the Vulkan VkSemaphore <vkSemaphore> when
151     <vkSemaphore> must be a valid Vulkan VkSemaphore non-dispatchable handle
158     causes the GL server to signal the Vulkan VkFence <vkFence> object when
161     <vkFence> must be a valid Vulkan VkFence non-dispatcable handle otherwise
204     contents of the Vulkan image <vkImage>.  The four corners of this
283     1) Can Vulkan entry points obtained through the typical Vulkan loader
286        UNRESOLVED: Vulkan entry points obtained through the Vulkan loader may
287        introduce layers between the application and the Vulkan driver.  These
288        layers may modify the Vulkan non-dispatchable handles returned by the
289        Vulkan driver.  In that case, these handles will not functions correctly
290        when used with OpenGL interop.  It is therefore advised the Vulkan layers