• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1// Copyright 2018-2021 The Khronos Group Inc.
2//
3// SPDX-License-Identifier: CC-BY-4.0
4
5include::{generated}/meta/{refprefix}VK_EXT_acquire_xlib_display.txt[]
6
7=== Other Extension Metadata
8
9*Last Modified Date*::
10    2016-12-13
11*IP Status*::
12    No known IP claims.
13*Contributors*::
14  - Dave Airlie, Red Hat
15  - Pierre Boudier, NVIDIA
16  - James Jones, NVIDIA
17  - Damien Leone, NVIDIA
18  - Pierre-Loup Griffais, Valve
19  - Liam Middlebrook, NVIDIA
20  - Daniel Vetter, Intel
21
22=== Description
23
24This extension allows an application to take exclusive control on a display
25currently associated with an X11 screen.
26When control is acquired, the display will be deassociated from the X11
27screen until control is released or the specified display connection is
28closed.
29Essentially, the X11 screen will behave as if the monitor has been unplugged
30until control is released.
31
32include::{generated}/interfaces/VK_EXT_acquire_xlib_display.txt[]
33
34=== Issues
35
361) Should flink:vkAcquireXlibDisplayEXT take an RandR display ID, or a
37Vulkan display handle as input?
38
39*RESOLVED*: A Vulkan display handle.
40Otherwise there would be no way to specify handles to displays that had been
41prevented from being included in the X11 display list by some native
42platform or vendor-specific mechanism.
43
442) How does an application figure out which RandR display corresponds to a
45Vulkan display?
46
47*RESOLVED*: A new function, flink:vkGetRandROutputDisplayEXT, is introduced
48for this purpose.
49
503) Should flink:vkGetRandROutputDisplayEXT be part of this extension, or a
51general Vulkan / RandR or Vulkan / Xlib extension?
52
53*RESOLVED*: To avoid yet another extension, include it in this extension.
54
55=== Version History
56
57 * Revision 1, 2016-12-13 (James Jones)
58   - Initial draft
59