mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-25 12:35:11 +00:00
* Update release number to 122. Internal Issues: * Add style guide language on not using standalone `+` signs (internal issue 736); not using leading whitespace for markup (internal issue 747); and on keeping descriptions of a single API in a contiguous block of markup (internal issue 949), and apply them to the specification. * Add a glossary definition of "`constant integral expression`", pointing to the SPIR-V "`constant instruction`" definition (internal issue 1225). * Many minor edits to improve writing style consistency and capture additional style guidelines (internal issue 1553). * Clarify that <<fragops-depth-write, depth writes are not performed>> if there is no depth framebuffer attachment (internal issue 1771). * Allow implementations to use rectangular line style of interpolation for <<primsrast-lines-bresenham, wide Bresenham lines>>, though replicating attributes is still preferred. Clarify that code:FragCoord is not replicated (internal issue 1772). * Resolve a contradiction in valid usage statements for slink:VkImageCreateInfo and slink:VkImageStencilUsageCreateInfoEXT (internal issue 1773). * Add style guide discussion of markup for indented equations, and use markup workaround for asciidoctor 2 compatibility (internal issue 1793). * Deprecate the `<<VK_EXT_validation_flags>>` extension in `vk.xml` and the extension appendix (internal issue 1801). * Add a new checker script `scripts/xml_consistency.py`. This is not currently run as part of internal CI (internal merge request 3285). * Correct "`an`" -> "`a`" prepositions where needed (internal merge request 3334). * Clarify that the <<features-uniformBufferStandardLayout, pname:uniformBufferStandardLayout>> feature is only required when the extension defining it is supported (internal merge request 3341). * Bring scripts into closer sync with OpenXR, mainly through conversion of comments to docstrings where appropriate, and add gen-scripts-docs.sh (internal merge request 3324). * Correct pname:maxDrawMeshTasksCount to 2^16^-1 in the <<limits-required, Required Limits>> table (internal merge requests 3361). New Extensions * `<<VK_IMG_format_pvrtc>>` (public issue 512).
66 lines
1.7 KiB
Plaintext
66 lines
1.7 KiB
Plaintext
include::meta/VK_EXT_acquire_xlib_display.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2016-12-13
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Dave Airlie, Red Hat
|
|
- Pierre Boudier, NVIDIA
|
|
- James Jones, NVIDIA
|
|
- Damien Leone, NVIDIA
|
|
- Pierre-Loup Griffais, Valve
|
|
- Liam Middlebrook, NVIDIA
|
|
- Daniel Vetter, Intel
|
|
|
|
This extension allows an application to take exclusive control on a display
|
|
currently associated with an X11 screen.
|
|
When control is acquired, the display will be deassociated from the X11
|
|
screen until control is released or the specified display connection is
|
|
closed.
|
|
Essentially, the X11 screen will behave as if the monitor has been unplugged
|
|
until control is released.
|
|
|
|
=== New Enum Constants
|
|
|
|
None.
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structures
|
|
|
|
None.
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkAcquireXlibDisplayEXT
|
|
* flink:vkGetRandROutputDisplayEXT
|
|
|
|
=== Issues
|
|
|
|
1) Should flink:vkAcquireXlibDisplayEXT take an RandR display ID, or a
|
|
Vulkan display handle as input?
|
|
|
|
*RESOLVED*: A Vulkan display handle.
|
|
Otherwise there would be no way to specify handles to displays that had been
|
|
"`blacklisted`" or prevented from being included in the X11 display list by
|
|
some native platform or vendor-specific mechanism.
|
|
|
|
2) How does an application figure out which RandR display corresponds to a
|
|
Vulkan display?
|
|
|
|
*RESOLVED*: A new function, flink:vkGetRandROutputDisplayEXT, is introduced
|
|
for this purpose.
|
|
|
|
3) Should flink:vkGetRandROutputDisplayEXT be part of this extension, or a
|
|
general Vulkan / RandR or Vulkan / Xlib extension?
|
|
|
|
*RESOLVED*: To avoid yet another extension, include it in this extension.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2016-12-13 (James Jones)
|
|
- Initial draft
|