Jon Leech df88ded281 Change log for September 5, 2017 Vulkan 1.0.60 spec update:
* 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`
2017-09-04 03:06:55 -07:00

168 lines
5.5 KiB
Plaintext

// Copyright (c) 2015-2017 Khronos Group. This work is licensed under a
// Creative Commons Attribution 4.0 International License; see
// http://creativecommons.org/licenses/by/4.0/
[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, Unity
* 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, Unity
* 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.