Vulkan-Docs/appendices/VK_KHR_get_display_properties2.txt
Jon Leech f1a7c4b4f3 Change log for January 13, 2019 Vulkan 1.1.98 spec update:
* Update release number to 98.

Public Issues:

  * Fix missing markup in flink:vkDestroyPipelineLayout valid usage
    statement (pull request 882).
  * Add missing contributors for `<<VK_EXT_buffer_device_address>>` (public
    pull request 891).

Internal Issues:

  * Detect nested bullet points in valid usage blocks and warn about them
    during VUID assignment (internal issue 1382).
  * Update the style guide to document the process for reserving new bits in
    bitmask types (internal issue 1411).
  * Clarify for slink:VkApplicationInfo::pname:apiVersion and in the
    <<fundamentals-validusage-versions, Valid Usage for Newer Core
    Versions>> section when it is valid for an application to use a certain
    version of Vulkan API functionality (for an instance and for a
    device/physical device); and when the validation layers must generate an
    error (internal issue 1412).
  * Add optional <<memory-model-availability-visibility, transitive
    availability/visibility operations to the memory model, including a new
    pname:vulkanMemoryModelAvailabilityVisibilityChains feature for
    slink:VkPhysicalDeviceVulkanMemoryModelFeaturesKHR (internal issue
    1460).
  * Add the code:StorageBuffer storage class to those in the
    <<interfaces-resources-descset, Descriptor Set Interface>> (internal
    issue 1480).
  * Add missing `returnedonly` tags for a number of returned extension
    structures that can be passed in pname:pNext chains (internal issue
    1515).
  * Clean up and rearrange some spec language for
    slink:VkRenderPassCreateInfo and slink:VkAttachmentReference.txt
    (internal issue 1522).
  * Correctly round the code:OpVectorTimesScalar and
    code:OpMatrixTimesScalar SPIR-V operations in the <<Precision of core
    SPIR-V Instructions>> table (internal merge request 2996).
  * Work around cases in flink:vkCmdBeginTransformFeedbackEXT,
    flink:vkCmdEndTransformFeedbackEXT, and
    slink:VkPipelineCoverageModulationStateCreateInfoNV where an array
    parameter is `optional` but the length is not in `vk.xml`. This is an
    interim fix using `noautovalidity` + handcoded VU replacing those that
    should be autogenerated (internal issue 2944 and
    https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/480).
  * Remove redundant capability validation of the code:float16 and code:int8
    SPIR-V capabilities from the <<spirvenv-capabilities, Capabilities>>
    section, since they are already covered in the preceding table.
  * Update check_spec_links script, including validation for reference page
    open blocks. Fix errors identified by the script.
2019-01-13 05:53:27 -08:00

91 lines
2.6 KiB
Plaintext

// Copyright (c) 2017-2019 Khronos Group. This work is licensed under a
// Creative Commons Attribution 4.0 International License; see
// http://creativecommons.org/licenses/by/4.0/
include::meta/VK_KHR_get_display_properties2.txt[]
*Last Modified Date*::
2017-02-21
*IP Status*::
No known IP claims.
*Contributors*::
- Ian Elliott, Google
- James Jones, NVIDIA
This extension provides new entry points to query device display properties
and capabilities in a way that can be easily extended by other extensions,
without introducing any further entry points.
This extension can be considered the <<VK_KHR_display,VK_KHR_display>>
equivalent of the <<VK_KHR_get_physical_device_properties2,
VK_KHR_get_physical_device_properties2>> extension.
=== New Object Types
None.
=== New Enum Constants
* Extending elink:VkStructureType:
** ename:VK_STRUCTURE_TYPE_DISPLAY_PROPERTIES_2_KHR
** ename:VK_STRUCTURE_TYPE_DISPLAY_PLANE_PROPERTIES_2_KHR
** ename:VK_STRUCTURE_TYPE_DISPLAY_MODE_PROPERTIES_2_KHR
** ename:VK_STRUCTURE_TYPE_DISPLAY_PLANE_INFO_2_KHR
** ename:VK_STRUCTURE_TYPE_DISPLAY_PLANE_CAPABILITIES_2_KHR
=== New Enums
None.
=== New Structures
* slink:VkDisplayProperties2KHR
* slink:VkDisplayPlaneProperties2KHR
* slink:VkDisplayModeProperties2KHR
* slink:VkDisplayPlaneInfo2KHR
* slink:VkDisplayPlaneCapabilities2KHR
=== New Functions
* flink:vkGetPhysicalDeviceDisplayProperties2KHR
* flink:vkGetPhysicalDeviceDisplayPlaneProperties2KHR
* flink:vkGetDisplayModeProperties2KHR
* flink:vkGetDisplayPlaneCapabilities2KHR
=== Issues
1) What should this extension be named?
*RESOLVED*: `VK_KHR_get_display_properties2`.
Other alternatives:
* `VK_KHR_display2`
* One extension, combined with `VK_KHR_surface_capabilites2`.
2) Should extensible input structs be added for these new functions:
*RESOLVED*:
* flink:vkGetPhysicalDeviceDisplayProperties2KHR: No.
The only current input is a slink:VkPhysicalDevice.
Other inputs wouldn't make sense.
* flink:vkGetPhysicalDeviceDisplayPlaneProperties2KHR: No.
The only current input is a slink:VkPhysicalDevice.
Other inputs wouldn't make sense.
* flink:vkGetDisplayModeProperties2KHR: No.
The only current inputs are a slink:VkPhysicalDevice and a
slink:VkDisplayModeKHR.
Other inputs wouldn't make sense.
3) Should additional display query functions be extended?
*RESOLVED*:
* flink:vkGetDisplayPlaneSupportedDisplaysKHR: No.
Extensions should instead extend
flink:vkGetDisplayPlaneCapabilitiesKHR().
=== Version History
* Revision 1, 2017-02-21 (James Jones)
- Initial draft.