Change log for September 5, 2017 Vulkan 1.0.60 spec update:
* 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`
2017-09-04 10:06:55 +00:00
|
|
|
include::meta/VK_EXT_display_control.txt[]
|
Change log for January 23, 2017 Vulkan 1.0.39 spec update:
* Bump API patch number and header version number to 39 for this update.
Github Issues:
* Clarified that only accesses via the specified buffer/image subresource
ranges are included in the access scopes (public issue 306).
* Add missing valid usage statements for flink:vkCreateComputePipelines
and flink:vkCreateGraphicsPipelines (public issue 427).
Internal Issues:
* Add a Note to the <<invariance,Invariance>> appendix about a difference
between OpenGL and Vulkan with regards to how primitives derived from
offsets are handled (internal issue 355).
* Add the +<<VK_KHR_get_physical_device_properties2>>+,
+<<VK_KHR_maintenance1>>+, and +<<VK_KHR_shader_draw_parameters>>+
extensions (internal issue 448).
* Add the +<<VK_EXT_shader_subgroup_vote>>+ and
+<<VK_EXT_shader_subgroup_ballot>>+ extensions (internal issue 449).
* Update the texture level-of-detail equation in the
<<textures-scale-factor,Scale Factor Operation>> section to better
approximate the ellipse major and minor axes (internal issue 547).
* Forbid non-explicitly allowed uses of interface decorations in the
introduction to the <<interfaces,Shader Interfaces>> chapter (internal
issue 607).
* Replace use of MathJax with KaTeX, for improved load-time performance as
well as avoiding the scrolling-and-scrolling behavior due to MathJax
asynchronous rendering when loading at an anchor inside the spec. This
change also requires moving to HTML5 output for the spec instead of
XHTML, and there is a visible difference in that the chapter navigation
index is now in a scrollable sidebar instead of at the top of the
document. We may or may not retain the nav sidebar based on feedback
(internal issue 613).
* Improve consistency of markup and formatting in extension appendices
(internal issue 631).
Other Issues:
* Add explicit valid usage statements to slink:VkImageCopy requiring that
the source and destination layer ranges be contained in their respective
source and destination images.
* Add valid usage language for swapchain of flink:vkAcquireNextImage. If
the swapchain has been replaced, then it should not be passed to
flink:vkAcquireNextImage.
* Add a valid usage statement to flink:vkCreateImageView, that the image
must have been created with an appropriate usage bit set.
* Noted that slink:VkDisplayPresentInfoKHR is a valid extension of
slink:VkPresentInfoKHR in the <<wsi_swapchain,WSI Swapchain>> section.
* Update valid usage for flink:vkCmdSetViewport and flink:vkCmdSetScissor
to account for the multiple viewport feature. If the feature is not
enabled, the parameters for these functions have required values that
are defined in the <<features-features-multiViewport,multiple
viewports>> section of the spec but were not reflected in the valid
usage text for these functions.
* Add the +<<VK_EXT_swapchain_colorspace>>+ extension defining common
color spaces.
2017-01-18 04:11:25 +00:00
|
|
|
|
|
|
|
|
*Last Modified Date*::
|
|
|
|
|
2016-12-13
|
|
|
|
|
*IP Status*::
|
|
|
|
|
No known IP claims.
|
|
|
|
|
*Contributors*::
|
|
|
|
|
- Pierre Boudier, NVIDIA
|
|
|
|
|
- James Jones, NVIDIA
|
|
|
|
|
- Damien Leone, NVIDIA
|
|
|
|
|
- Pierre-Loup Griffais, Valve
|
|
|
|
|
- Daniel Vetter, Intel
|
|
|
|
|
|
|
|
|
|
This extension defines a set of utility functions for use with the
|
|
|
|
|
+VK_KHR_display+ and +VK_KHR_display_swapchain+ extensions.
|
|
|
|
|
|
|
|
|
|
=== New Enum Constants
|
|
|
|
|
|
2017-06-05 03:48:43 +00:00
|
|
|
* Extending elink:VkStructureType:
|
Change log for January 23, 2017 Vulkan 1.0.39 spec update:
* Bump API patch number and header version number to 39 for this update.
Github Issues:
* Clarified that only accesses via the specified buffer/image subresource
ranges are included in the access scopes (public issue 306).
* Add missing valid usage statements for flink:vkCreateComputePipelines
and flink:vkCreateGraphicsPipelines (public issue 427).
Internal Issues:
* Add a Note to the <<invariance,Invariance>> appendix about a difference
between OpenGL and Vulkan with regards to how primitives derived from
offsets are handled (internal issue 355).
* Add the +<<VK_KHR_get_physical_device_properties2>>+,
+<<VK_KHR_maintenance1>>+, and +<<VK_KHR_shader_draw_parameters>>+
extensions (internal issue 448).
* Add the +<<VK_EXT_shader_subgroup_vote>>+ and
+<<VK_EXT_shader_subgroup_ballot>>+ extensions (internal issue 449).
* Update the texture level-of-detail equation in the
<<textures-scale-factor,Scale Factor Operation>> section to better
approximate the ellipse major and minor axes (internal issue 547).
* Forbid non-explicitly allowed uses of interface decorations in the
introduction to the <<interfaces,Shader Interfaces>> chapter (internal
issue 607).
* Replace use of MathJax with KaTeX, for improved load-time performance as
well as avoiding the scrolling-and-scrolling behavior due to MathJax
asynchronous rendering when loading at an anchor inside the spec. This
change also requires moving to HTML5 output for the spec instead of
XHTML, and there is a visible difference in that the chapter navigation
index is now in a scrollable sidebar instead of at the top of the
document. We may or may not retain the nav sidebar based on feedback
(internal issue 613).
* Improve consistency of markup and formatting in extension appendices
(internal issue 631).
Other Issues:
* Add explicit valid usage statements to slink:VkImageCopy requiring that
the source and destination layer ranges be contained in their respective
source and destination images.
* Add valid usage language for swapchain of flink:vkAcquireNextImage. If
the swapchain has been replaced, then it should not be passed to
flink:vkAcquireNextImage.
* Add a valid usage statement to flink:vkCreateImageView, that the image
must have been created with an appropriate usage bit set.
* Noted that slink:VkDisplayPresentInfoKHR is a valid extension of
slink:VkPresentInfoKHR in the <<wsi_swapchain,WSI Swapchain>> section.
* Update valid usage for flink:vkCmdSetViewport and flink:vkCmdSetScissor
to account for the multiple viewport feature. If the feature is not
enabled, the parameters for these functions have required values that
are defined in the <<features-features-multiViewport,multiple
viewports>> section of the spec but were not reflected in the valid
usage text for these functions.
* Add the +<<VK_EXT_swapchain_colorspace>>+ extension defining common
color spaces.
2017-01-18 04:11:25 +00:00
|
|
|
** ename:VK_STRUCTURE_TYPE_DISPLAY_POWER_INFO_EXT
|
|
|
|
|
** ename:VK_STRUCTURE_TYPE_DEVICE_EVENT_INFO_EXT
|
|
|
|
|
** ename:VK_STRUCTURE_TYPE_DISPLAY_EVENT_INFO_EXT
|
|
|
|
|
** ename:VK_STRUCTURE_TYPE_SWAPCHAIN_COUNTER_CREATE_INFO_EXT
|
|
|
|
|
|
|
|
|
|
=== New Enums
|
|
|
|
|
|
|
|
|
|
* elink:VkDisplayPowerStateEXT
|
|
|
|
|
* elink:VkDeviceEventTypeEXT
|
|
|
|
|
* elink:VkDisplayEventTypeEXT
|
|
|
|
|
|
|
|
|
|
=== New Structures
|
|
|
|
|
|
|
|
|
|
* slink:VkDisplayPowerInfoEXT
|
|
|
|
|
* slink:VkDeviceEventInfoEXT
|
|
|
|
|
* slink:VkDisplayEventInfoEXT
|
|
|
|
|
* slink:VkSwapchainCounterCreateInfoEXT
|
|
|
|
|
|
|
|
|
|
=== New Functions
|
|
|
|
|
|
|
|
|
|
* flink:vkDisplayPowerControlEXT
|
|
|
|
|
* flink:vkRegisterDeviceEventEXT
|
|
|
|
|
* flink:vkRegisterDisplayEventEXT
|
|
|
|
|
* flink:vkGetSwapchainCounterEXT
|
|
|
|
|
|
|
|
|
|
=== Issues
|
|
|
|
|
|
|
|
|
|
1) Should this extension add an explicit "WaitForVsync" API or a fence
|
|
|
|
|
signaled at vsync that the application can wait on?
|
|
|
|
|
|
|
|
|
|
*RESOLVED*: A fence.
|
|
|
|
|
A separate API could later be provided that allows exporting the fence to a
|
|
|
|
|
native object that could be inserted into standard run loops on POSIX and
|
|
|
|
|
Windows systems.
|
|
|
|
|
|
|
|
|
|
2) Should callbacks be added for a vsync event, or in general to monitor
|
|
|
|
|
events in Vulkan?
|
|
|
|
|
|
|
|
|
|
*RESOLVED*: No, fences should be used.
|
|
|
|
|
Some events are generated by interrupts which are managed in the kernel.
|
|
|
|
|
In order to use a callback provided by the application, drivers would need
|
|
|
|
|
to have the userspace driver spawn threads that would wait on the kernel
|
|
|
|
|
event, and hence the callbacks could be difficult for the application to
|
|
|
|
|
synchronize with its other work given they would arrive on a foreign thread.
|
|
|
|
|
|
|
|
|
|
3) Should vblank or scanline events be exposed?
|
|
|
|
|
|
|
|
|
|
*RESOLVED*: Vblank events.
|
|
|
|
|
Scanline events could be added by a separate extension, but the latency of
|
|
|
|
|
processing an interrupt and waking up a userspace event is high enough that
|
|
|
|
|
the accuracy of a scanline event would be rather low.
|
|
|
|
|
Further, per-scanline interrupts are not supported by all hardware.
|
|
|
|
|
|
|
|
|
|
=== Version History
|
|
|
|
|
|
|
|
|
|
* Revision 1, 2016-12-13 (James Jones)
|
|
|
|
|
- Initial draft
|