Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
Change log for March 3, 2019 Vulkan 1.1.102 spec update:
* Update release number to 102. Public Issues: * Simplify flink:vkGetImageMemoryRequirements constraint for ename:VK_MEMORY_PROPERTY_LAZILY_ALLOCATED_BIT (public pull request 817). * Fix typo in markup of the <<textures-texel-coordinate-systems-diagrams, Texel Coordinate Systems, Corner Sampling>> image that was generating complaints from chunked HTML output generation (public pull request 928). Internal Issues: * Split the old <<features, Features>> chapter into four chapters: <<features, Features>>, <<limits, Limits>>, <<formats, Formats>>, and <<capabilities, Capabilities>>, with minor edits to the introductory paragraph of each chapter. Anchor names in these chapters were changed, with corresponding effects to xrefs to these anchors elsewhere in spec markup . The purpose is to make the chunked HTML spec output load faster on what was previously a single, gigantic chapter (internal issue 1554). * Add ename:VK_PIPELINE_STAGE_RAY_TRACING_SHADER_BIT_NV, to the supported pipeline stages for ename:VK_ACCESS_UNIFORM_READ, ename:VK_ACCESS_SHADER_READ, and ename:VK_ACCESS_SHADER_WRITE in the <<synchronization-access-types-supported>> table. * Correct legal name of Google, LLC in vk.xml \<tags> section and a copyright statement. * Clarify that Vulkan treats the Android code:AHARDWAREBUFFER_FORMAT_R8G8B8X8_UNORM format as RGBA, and the application is responsible for forcing the X/A component to be read as 1.0, in the <<memory-external-android-hardware-buffer-formats>> table. * Clarify the vertex order of various primitive topologies, and define the order of transform feedback vertex capture based on that. This involves a lot of refactoring and cleanup in the <<drawing-primitive-topologies, Primitive Topologies>>, <<geometry-input, Geometry Shader Input Primitives>> sections, and <<vertexpostproc-transform-feedback Transform Feedback>> sections, and numerous places in the <<tessellation>> chapter, New Extensions: * `VK_EXT_metal_surface` * `VK_EXT_ycbcr_image_arrays` (internal issue 1361). * `VK_NVX_image_view_handle`
- Loading branch information
Showing
77 changed files
with
11,253 additions
and
9,355 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
include::meta/VK_EXT_metal_surface.txt[] | ||
|
||
*Last Modified Date*:: | ||
2018-10-01 | ||
*IP Status*:: | ||
No known IP claims. | ||
*Contributors*:: | ||
- Dzmitry Malyshau, Mozilla Corp. | ||
|
||
The `VK_EXT_metal_surface` extension is an instance extension. | ||
It provides a mechanism to create a slink:VkSurfaceKHR object (defined by | ||
the `<<VK_KHR_surface>>` extension) from dlink:CAMetalLayer, which is the | ||
native rendering surface of Apple's Metal framework. | ||
|
||
=== New Object Types | ||
|
||
None. | ||
|
||
=== New Enum Constants | ||
|
||
* Extending elink:VkStructureType: | ||
** ename:VK_STRUCTURE_TYPE_METAL_SURFACE_CREATE_INFO_EXT | ||
|
||
=== New Enums | ||
|
||
None. | ||
|
||
=== New Structures | ||
|
||
* slink:VkMetalSurfaceCreateInfoEXT | ||
|
||
=== New Functions | ||
|
||
* flink:vkCreateMetalSurfaceEXT | ||
|
||
=== Issues | ||
|
||
None. | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2018-10-01 (Dzmitry Malyshau) | ||
- Initial version |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
// Copyright (c) 2018-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_EXT_ycbcr_image_arrays.txt[] | ||
|
||
Last Modified Date:: | ||
2019-01-15 | ||
Contributors:: | ||
- Piers Daniell, NVIDIA | ||
|
||
This extension allows images of a format that requires | ||
<<formats-requiring-sampler-ycbcr-conversion, Y'C~B~C~R~ conversion>> to be | ||
created with multiple array layers, which is otherwise restricted. | ||
|
||
=== New Enum Constants | ||
|
||
* Extending elink:VkStructureType: | ||
** ename:VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_YCBCR_IMAGE_ARRAYS_FEATURES_EXT | ||
|
||
=== New Enums | ||
|
||
None. | ||
|
||
=== New Structures | ||
|
||
* slink:VkPhysicalDeviceYcbcrImageArraysFeaturesEXT | ||
|
||
=== New Functions | ||
|
||
None. | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2019-01-15 (Piers Daniell) | ||
- Initial revision | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
include::meta/VK_NVX_image_view_handle.txt[] | ||
|
||
*Last Modified Date*:: | ||
2018-12-07 | ||
*Contributors*:: | ||
- Eric Werness, NVIDIA | ||
- Jeff Bolz, NVIDIA | ||
- Daniel Koch, NVIDIA | ||
|
||
This extension allows applications to query an opaque handle from an image | ||
view for use as a sampled image or storage image. | ||
This provides no direct functionality itself. | ||
|
||
=== New Object Types | ||
|
||
None. | ||
|
||
=== New Enum Constants | ||
|
||
* Extending elink:VkStructureType: | ||
** ename:VK_STRUCTURE_TYPE_IMAGE_VIEW_HANDLE_INFO_NVX | ||
|
||
=== New Enums | ||
|
||
None. | ||
|
||
=== New Structures | ||
|
||
* slink:VkImageViewHandleInfoNVX | ||
|
||
=== New Functions | ||
|
||
* flink:vkGetImageViewHandleNVX | ||
|
||
=== Issues | ||
|
||
None. | ||
|
||
=== Version History | ||
|
||
* Revision 1, 2018-12-07 (Eric Werness) | ||
- Internal revisions |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.