mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-12 23:14:20 +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`
77 lines
2.3 KiB
Plaintext
77 lines
2.3 KiB
Plaintext
include::meta/VK_EXT_display_control.txt[]
|
|
|
|
*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
|
|
|
|
* Extending elink:VkStructureType:
|
|
** 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
|