mirror of
https://github.com/status-im/Vulkan-Docs.git
synced 2025-01-11 14:34:08 +00:00
b9e9296cd8
* Bump API patch number and header version number to 53 for this update.
Github Issues:
Internal Issues:
* Clarify mappings of coordinates for mutable, compatible image views in
slink:VkImageViewCreateInfo (internal issue 815).
* Make ename:VK_BIND_SFR_BIT require a logical device with multiple
physical devices, so that standard sparse image block dimensions are
only required on systems that support multi-GPU (internal issue 835).
* Convert all files from use of // refBegin .. // refEnd comments to
delimit ref pages, to use of open blocks, and update style guide
accordingly (internal issue 839).
* Add valid usage for slink:VkWriteDescriptorSet when performing updates
to a ename:VK_STORAGE_IMAGE descriptor with layout
ename:VK_IMAGE_LAYOUT_GENERAL.
* Add a hack to the validity generator script to support an odd
interaction between flink:vkCmdFillBuffer and an extension (internal
issue 853).
* Remove redundant text describing slink:VkBufferCreateInfo::pname:usage,
which was already covered by implicit valid usage (internal issue 854).
* Update implicit validity generator script to properly handle the
pname:sType and pname:pNext members of "returnedonly" structures
(internal issue 874).
* Note that slink:VkApplicationInfo::pname:pApplicationName &
slink:VkApplicationInfo::pname:pEngineName are optional, and add missing
implicit valid usage statements for flink:vkDestroyInstance.
* Added missing valid usage for flink:vkCmdWriteTimestamp to require a
timestamp query pool.
* Simplify and/or split "`non-atomic`" valid usage statements.
New Extensions:
* `VK_AMD_gpu_shader_int16`
* `VK_EXT_blend_operation_advanced`
* `VK_EXT_sampler_filter_minmax`
* `VK_NV_framebuffer_mixed_samples`
-----------------------------------------------------
Note: the 1.0.52 spec wasn't published on github, so the 1.0.53 release
combines both change sets.
-----------------------------------------------------
Change log for June 13, 2017 Vulkan 1.0.52 spec update:
* Bump API patch number and header version number to 52 for this update.
Github Issues:
Internal Issues:
* Clarify behavior when non-coherent memory has
<<memory-device-unmap-does-not-flush, not been flushed before being
unmapped>> (internal issue 819).
* Fix description of code:WorkgroupSize builtin to note it decorates an
object, not a variable (internal issue 836).
* Fix asciidoc attributes so that trailing '{plus}' symbols in [eq] style
equations are rendered properly (internal issue 845).
* Add language to the "`Extension Handles, Objects, Enums, and Typedefs`"
section of the Procedures and Conventions document stating that any new
handle type requires a corresponding entry in the elink:VkObjectType
enumerated type (internal issue 856).
* Update style guide to use slink macro for Vulkan handle type names, and
define narrow conditions under which to use the *name and *text macros
instead of *link (internal issue 886).
* Add a dependency of the <<VK_KHX_device_group,VK_KHX_device_group>>
extension on VK_KHX_device_group_creation to +vk.xml+ and the extension
appendix.
* Change the copyright on Vulkan specification asciidoc *source* files to
CC-BY 4.0, and update the proprietary Khronos copyright applied to the
generated *output* formats (internal issue 327). This enables broader
re-use and modification of the Vulkan specification sources, while not
affecting the Reciprocal IP License between Vulkan Adopters and Working
Group Members.
New Extensions:
* `VK_NV_fill_rectangle`
* `VK_NV_fragment_coverage_to_color`
2.3 KiB
2.3 KiB
The files in, and generated output documents from this Vulkan-Docs project are under a mix of copyright and license statements. Refer to the individual files for specific information. As a general guideline:
- The Vulkan Specification asciidoc sources, as well as other documentation which we expect people may wish to regenerate and distributed in other formats - such as the reference pages generated from the Specification source - are under a Creative Commons Attribution 4.0 license. ** The specification sources have only recently (as of June 2017) been placed under this license. We will now be able to accept pull requests on Github, but there is a related Contribution License Agreement which people proposing PRs to the Vulkan-Docs repository must execute as part of opening the PR.
- Generated output documents, including the official Vulkan Specification PDF and HTML documents, are under a proprietary Khronos license. See https://www.khronos.org/registry/speccopyright.html . Only Specification documents posted in the Vulkan Registry are official.
- The Vulkan headers, spec build tools, and spec and registry configuration files are, for the most part, under the Apache 2 license. Some older files are under BSD-like licenses which may eventually be updated to Apache 2 as we have time.
- There may be some configuration files customized from material shipped with the asciidoc and dblatex distributions. Such files continue under their original copyrights.
- Some generated, transient files produced during the course of building the specification, headers, or other targets may not have copyrights. These are typically very short asciidoc fragments describing parts of the Vulkan API, and are incorporated by reference into specification or reference page builds.
- If something is missing a copyright statement and that poses an actual problem for whatever you're doing, file an issue on GitHub and we'll eventually correct it in some fashion.
Working with the different Khronos member company IP lawyers to make license changes is a very slow process constrained by the Khronos Member Agreement and IP Policy as well as by individual company concerns about their IP. Do not expect rapid changes in anything having to to with copyrights and licensing.