mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-02-22 02:58:16 +00:00
df88ded281
* Bump API patch number and header version number to 60 for this update.
Github Issues:
* Document that <<queries-timestamps, Timestamp Queries>> can only be
meaningfully compared when they are written from the same queue (public
issue 216).
* Document that the `<extension>` tag `type` attribute is required for
non-disabled extensions (derived from, but does not close public issue
354).
* Clean up registry schema length attribute descriptions to be consistent
and correct (public issue 555).
Internal Issues:
* Replace as much of the hand-written extension appendix metadata as
possible with asciidoc includes generated from corresponding attributes
of +vk.xml+, and enhance the style guide to match. This avoids
inconsistencies between +vk.xml+ and the appendices, and produces a more
uniform style (internal issue 137).
* Remove the generated extDependency.{py,sh} files from the tree and
create them dynamically on demand instead, reducing merge conflicts
(internal issue 713).
* Add a prototype tool for generating in-place difference markup for
sections guarded by asciidoc conditionals, and new syntax for open
blocks to support it (internal issue 833).
* Remove unnecessary restriction of etext:*SYNC_FD_BIT_KHR external handle
types to the same physical device in the
slink:VkPhysicalDeviceIDPropertiesKHR,
flink:VkImportMemoryWin32HandleInfoKHR,
slink:VkImportFenceWin32HandleInfoKHR, slink:VkImportFenceFdInfoKHR,
slink:VkImportSemaphoreWin32HandleInfoKHR,
slink:VkImportSemaphoreFdInfoKHR
<<external-memory-handle-types-compatibility, External memory handle
types compatibility>>, <<external-semaphore-handle-types-compatibility,
External semaphore handle types compatibility>>, and
<<external-fence-handle-types-compatibility, External fence handle types
compatibility>> sections (internal issue 956).
Other Issues:
* Remove dependency of +VK_KHX_device_group+ on +VK_KHR_swapchain+ (there
is an interaction, but not a strict dependency), and add a new
`extension` attribute to the `<require` XML tag to allow classifying a
subset of interfaces of an extension as requiring another extension.
Update the registry schema and documentation accordingly.
New Extensions:
* `VK_AMD_shader_fragment_mask` (and related `GL_AMD_shader_fragment_mask`
GLSL extension)
* `VK_EXT_sample_locations`
* `VK_EXT_validation_cache`
90 lines
2.6 KiB
Plaintext
90 lines
2.6 KiB
Plaintext
// Copyright (c) 2017 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_surface_capabilities2.txt[]
|
|
|
|
*Last Modified Date*::
|
|
2017-02-27
|
|
*IP Status*::
|
|
No known IP claims.
|
|
*Contributors*::
|
|
- Ian Elliott, Google
|
|
- James Jones, NVIDIA
|
|
- Alon Or-bach, Samsung
|
|
|
|
This extension provides new entry points to query device surface
|
|
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_surface,VK_KHR_surface>>
|
|
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_PHYSICAL_DEVICE_SURFACE_INFO_2_KHR
|
|
** ename:VK_STRUCTURE_TYPE_SURFACE_CAPABILITIES_2_KHR
|
|
** ename:VK_STRUCTURE_TYPE_SURFACE_FORMAT_2_KHR
|
|
|
|
=== New Enums
|
|
|
|
None.
|
|
|
|
=== New Structures
|
|
|
|
* slink:VkPhysicalDeviceSurfaceInfo2KHR
|
|
* slink:VkSurfaceCapabilities2KHR
|
|
* slink:VkSurfaceFormat2KHR
|
|
|
|
=== New Functions
|
|
|
|
* flink:vkGetPhysicalDeviceSurfaceCapabilities2KHR
|
|
* flink:vkGetPhysicalDeviceSurfaceFormats2KHR
|
|
|
|
=== Issues
|
|
|
|
1) What should this extension be named?
|
|
|
|
*RESOLVED*: VK_KHR_get_surface_capabilities2.
|
|
Other alternatives:
|
|
|
|
* VK_KHR_surface2
|
|
* One extension, combined with VK_KHR_get_display_properties2
|
|
|
|
2) Should additional WSI query functions be extended?
|
|
|
|
*RESOLVED*:
|
|
|
|
* flink:vkGetPhysicalDeviceSurfaceCapabilitiesKHR: Yes.
|
|
The need for this motivated the extension.
|
|
* flink:vkGetPhysicalDeviceSurfaceSupportKHR: No.
|
|
Currently only has boolean output.
|
|
Extensions should instead extend
|
|
flink:vkGetPhysicalDeviceSurfaceCapabilities2KHR.
|
|
* flink:vkGetPhysicalDeviceSurfaceFormatsKHR: Yes.
|
|
* flink:vkGetPhysicalDeviceSurfacePresentModesKHR: No.
|
|
Recent discussion concluded this introduced too much variability for
|
|
applications to deal with.
|
|
Extensions should instead extend
|
|
flink:vkGetPhysicalDeviceSurfaceCapabilities2KHR.
|
|
* flink:vkGetPhysicalDeviceXlibPresentationSupportKHR: Not in this
|
|
extension.
|
|
* flink:vkGetPhysicalDeviceXcbPresentationSupportKHR: Not in this
|
|
extension.
|
|
* flink:vkGetPhysicalDeviceWaylandPresentationSupportKHR: Not in this
|
|
extension.
|
|
* flink:vkGetPhysicalDeviceMirPresentationSupportKHR: Not in this
|
|
extension.
|
|
* flink:vkGetPhysicalDeviceWin32PresentationSupportKHR: Not in this
|
|
extension.
|
|
|
|
=== Version History
|
|
|
|
* Revision 1, 2017-02-27 (James Jones)
|
|
- Initial draft.
|