Jon Leech ca4abe0d34 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-17 20:11:25 -08:00

167 lines
5.5 KiB
Plaintext

// Copyright (c) 2015-2017 The Khronos Group Inc.
// Copyright notice at https://www.khronos.org/registry/speccopyright.html
[appendix]
[[credits]]
= Credits
Vulkan 1.0 is the result of contributions from many people and companies
participating in the Khronos Vulkan Working Group, as well as input from the
Vulkan Advisory Panel.
Members of the Working Group, including the company that they represented at
the time of their contributions, are listed below.
Some specific contributions made by individuals are listed together with
their name.
* Adam Jackson, Red Hat
* Adam Śmigielski, Mobica
* Alex Bourd, Qualcomm Technologies, Inc.
* Alexander Galazin, ARM
* Allen Hux, Intel
* Alon Or-bach, Samsung Electronics (WSI technical sub-group chair)
* Andrew Cox, Samsung Electronics
* Andrew Garrard, Samsung Electronics (format wrangler)
* Andrew Poole, Samsung Electronics
* Andrew Rafter, Samsung Electronics
* Andrew Richards, Codeplay Software Ltd.
* Andrew Woloszyn, Google
* Antoine Labour, Google
* Aras Pranckevičius, Unity
* Ashwin Kolhe, NVIDIA
* Ben Bowman, Imagination Technologies
* Benj Lipchak
* Bill Hollings, The Brenwill Workshop
* Bill Licea-Kane, Qualcomm Technologies, Inc.
* Brent E.
Insko, Intel
* Brian Ellis, Qualcomm Technologies, Inc.
* Cass Everitt, Oculus VR
* Cemil Azizoglu, Canonical
* Chad Versace, Intel
* Chang-Hyo Yu, Samsung Electronics
* Chia-I Wu, LunarG
* Chris Frascati, Qualcomm Technologies, Inc.
* Christophe Riccio, Unity
* Cody Northrop, LunarG
* Courtney Goeltzenleuchter, LunarG
* Damien Leone, NVIDIA
* Dan Baker, Oxide Games
* Dan Ginsburg, Valve
* Daniel Johnston, Intel
* Daniel Koch, NVIDIA (<<interfaces,Shader Interfaces>>;
<<features,Features, Limits, and Formats>>)
* Daniel Rakos, AMD
* David Airlie, Red Hat
* David Neto, Google
* David Mao, AMD
* David Yu, Pixar
* Dominik Witczak, AMD
* Frank (LingJun) Chen, Qualcomm Technologies, Inc.
* Fred Liao, Mediatek
* Gabe Dagani, Freescale
* Graeme Leese, Broadcom
* Graham Connor, Imagination Technologies
* Graham Sellers, AMD
* Hwanyong Lee, Kyungpook National University
* Ian Elliott, LunarG
* Ian Romanick, Intel
* James Jones, NVIDIA
* James Hughes, Oculus VR
* Jan Hermes, Continental Corporation
* Jan-Harald Fredriksen, ARM
* Jason Ekstrand, Intel
* Jeff Bolz, NVIDIA (extensive contributions, exhaustive review and
rewrites for technical correctness)
* Jeff Juliano, NVIDIA
* Jeff Vigil, Qualcomm Technologies, Inc.
* Jens Owen, LunarG
* Jeremy Hayes, LunarG
* Jesse Barker, ARM
* Jesse Hall, Google
* Johannes van Waveren, Oculus VR
* John Kessenich, Google (SPIR-V and GLSL for Vulkan spec author)
* John McDonald, Valve
* Jon Ashburn, LunarG
* Jon Leech, Independent (XML toolchain, normative language, release
wrangler)
* Jonas Gustavsson, Sony Mobile
* Jonathan Hamilton, Imagination Technologies
* Jungwoo Kim, Samsung Electronics
* Kenneth Benzie, Codeplay Software Ltd.
* Kerch Holt, NVIDIA (SPIR-V technical sub-group chair)
* Kristian Kristensen, Intel
* Krzysztof Iwanicki, Samsung Electronics
* Larry Seiler, Intel
* Lutz Latta, Lucasfilm
* Maria Rovatsou, Codeplay Software Ltd.
* Mark Callow
* Mark Lobodzinski, LunarG
* Mateusz Przybylski, Intel
* Mathias Heyer, NVIDIA
* Mathias Schott, NVIDIA
* Maxim Lukyanov, Samsung Electronics
* Maurice Ribble, Qualcomm Technologies, Inc.
* Michael Lentine, Google
* Michael Worcester, Imagination Technologies
* Michal Pietrasiuk, Intel
* Mika Isojarvi, Google
* Mike Stroyan, LunarG
* Minyoung Son, Samsung Electronics
* Mitch Singer, AMD
* Mythri Venugopal, Samsung Electronics
* Naveen Leekha, Google
* Neil Henning, Codeplay Software Ltd.
* Neil Trevett, NVIDIA
* Nick Penwarden, Epic Games
* Niklas Smedberg, Epic Games
* Norbert Nopper, Freescale
* Pat Brown, NVIDIA
* Patrick Doane, Blizzard Entertainment
* Peter Lohrmann, Valve
* Pierre Boudier, NVIDIA
* Pierre-Loup A.
Griffais, Valve
* Piers Daniell, NVIDIA (dynamic state, copy commands, memory types)
* Piotr Bialecki, Intel
* Prabindh Sundareson, Samsung Electronics
* Pyry Haulos, Google (Vulkan conformance test subcommittee chair)
* Ray Smith, ARM
* Rob Stepinski, Transgaming
* Robert J.
Simpson, Qualcomm Technologies, Inc.
* Rolando Caloca Olivares, Epic Games
* Roy Ju, Mediatek
* Rufus Hamede, Imagination Technologies
* Sean Ellis, ARM
* Sean Harmer, KDAB
* Shannon Woods, Google
* Slawomir Cygan, Intel
* Slawomir Grajewski, Intel
* Stefanus Du Toit, Google
* Steve Hill, Broadcom
* Steve Viggers, Core Avionics & Industrial Inc.
* Stuart Smith, Imagination Technologies
* Tim Foley, Intel
* Timo Suoranta, AMD
* Timothy Lottes, AMD
* Tobias Hector, Imagination Technologies (validity language and
toolchain)
* Tobin Ehlis, LunarG
* Tom Olson, ARM (working group chair)
* Tomasz Kubale, Intel
* Tony Barbour, LunarG
* Wayne Lister, Imagination Technologies
* Yanjun Zhang, Vivante
* Zhenghong Wang, Mediatek
In addition to the Working Group, the Vulkan Advisory Panel members provided
important real-world usage information and advice that helped guide design
decisions.
Administrative support to the Working Group was provided by members of Gold
Standard Group, including Andrew Riegel, Elizabeth Riegel, Glenn Fredericks,
Kathleen Mattson and Michelle Clark.
Technical support was provided by James Riordon, webmaster of Khronos.org
and OpenGL.org.