status-im/Vulkan-Docs
2
0
Fork 0
mirror of https://github.com/status-im/Vulkan-Docs.git synced 2025-01-11 22:44:11 +00:00
Code Issues Projects Releases Wiki Activity
Vulkan-Docs/appendices/VK_KHR_surface_protected_capabilities.txt

60 lines
1.6 KiB
Plaintext
Raw Permalink Normal View History

Change log for March 18, 2019 Vulkan 1.1.104 spec update: * Update release number to 104. Public Issues: * Remove the incorrect line from "`Initial`" to "`Invalid`" state in the <<commandbuffer-lifecycle-diagram, Lifecycle of a command buffer>> diagram (public issue 881). * Add Fuchsia platform to <<boilerplate-wsi-header-table, Window System Extensions and Headers>> table (public pull request 933). * Change the type of slink:VkBufferDeviceAddressCreateInfoEXT::pname:deviceAddress from basetype:VkDeviceSize to basetype:VkDeviceAddress. These are both typedefs of code:uint64_t, so it is an ABI-compatible change (public issue 934). Internal Issues: * Remove generated header files and update the CI tests to build a copy of the headers for use by the hpp-generate / hpp-compile CI stages. Targets to generate the headers will not be removed, but keeping these generated files in the repository increased the frequency of conflicts between branches when merging to master (internal issue 745). * Reword "`undefined: behavior if *action*" to "`must: not do *action*`" in the places the old terminology was used, and add a new <<writing-undefined, Describing Undefined Behavior>> section of the style guide to explain how to write such language in the future (internal issue 1579). * Move almost all Python scripts into the toplevel `scripts/` directory. Apply extensive internal edits to clean up and simplify the scripts, and try to follow PEP8 guidelines. Generalize the scripts with the use of a Conventions object controlling many aspects of output generation, to enable their use in other Khronos projects with similar requirements. Autogenerate extension interface refpages (these are experimental and may be retired going forward). New Extensions: * `VK_AMD_display_native_hdr` * `VK_EXT_full_screen_exclusive` (internal issue 1439) * `VK_EXT_host_query_reset` * `VK_EXT_pipeline_creation_feedback` (internal issue 1560) * `VK_KHR_surface_protected_capabilities` (internal issue 1520)
2019-03-17 06:05:46 -07:00
include::meta/VK_KHR_surface_protected_capabilities.txt[]
*Last Modified Date*::
2018-12-18
*IP Status*::
No known IP claims.
*Contributors*::
- Sandeep Shinde, NVIDIA
- James Jones, NVIDIA
- Daniel Koch, NVIDIA
This extension extends slink:VkSurfaceCapabilities2KHR, providing
applications a way to query whether swapchains can: be created with the
ename:VK_SWAPCHAIN_CREATE_PROTECTED_BIT_KHR flag set.
Vulkan 1.1 added (optional) support for protect memory and protected
resources including buffers (ename:VK_BUFFER_CREATE_PROTECTED_BIT), images
(ename:VK_IMAGE_CREATE_PROTECTED_BIT), and swapchains
(ename:VK_SWAPCHAIN_CREATE_PROTECTED_BIT_KHR).
However, on implementations which support multiple windowing systems, not
all window systems may: be able to provide a protected display path.
This extension provides a way to query if a protected swapchain created for
a surface (and thus a specific windowing system) can: be displayed on
screen.
It extends the existing slink:VkSurfaceCapabilities2KHR structure with a new
slink:VkSurfaceProtectedCapabilitiesKHR structure from which the application
can: obtain information about support for protected swapchain creation
through flink:vkGetPhysicalDeviceSurfaceCapabilities2KHR.
=== New Object Types
None.
=== New Enum Constants
* Extending elink:VkStructureType:
** ename:VK_STRUCTURE_TYPE_SURFACE_PROTECTED_CAPABILITIES_KHR
=== New Enums
None.
=== New Structures
* slink:VkSurfaceProtectedCapabilitiesKHR
=== New Functions
None.
=== Issues
None.
=== Version History
* Revision 1, 2018-12-18 (Sandeep Shinde, Daniel Koch)
- Internal revisions.
Reference in New Issue Copy Permalink