Add multi-format sysmem entrypoints

These entrypoints will allow applications to specify that they can
handle multiple different image formats in a buffer collection. This
will allow us to remove a hack from ImagePipe2, where it uses
VK_FORMAT_UNDEFINED to allow that it supports any format that the driver
supports.

Bug: fxb/54503

Change-Id: Ifb0c1dd5d07000d910fe46750b0dcc002949a1c4
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/Vulkan-Headers/+/421196
Reviewed-by: John Rosasco <rosasco@google.com>
Reviewed-by: Craig Stout <cstout@google.com>
4 files changed
tree: 4ca7670fe3a4780afaa7a30a6f9ce9c23efcee8f
  1. cmake/
  2. include/
  3. registry/
  4. .cmake-format.py
  5. .gitattributes
  6. .gitignore
  7. BUILD.gn
  8. BUILD.md
  9. CMakeLists.txt
  10. CODE_OF_CONDUCT.md
  11. LICENSE.txt
  12. README.fuchsia
  13. README.md
README.md

Vulkan-Headers

Vulkan header files and API registry

Repository Content

The contents of this repository are largely obtained from other repositories and are collected, coordinated, and curated here.

Do not propose pull requests to this repository which modify any files under include/vulkan/ or registry/. All such files are generated from the Vulkan-Docs repository and, in the case of include/vulkan/vulkan.hpp, the Vulkan-Hpp repository. Any changes must be made in those repositories.

The projects for these repositories are:

Please visit the appropriate project in the above list for obtaining additional information, asking questions, or opening issues.

Version Tagging Scheme

Updates to the Vulkan-Headers repository which correspond to a new Vulkan specification release are tagged using the following format: v<version> (e.g., v1.1.96).

Note: Marked version releases have undergone thorough testing but do not imply the same quality level as SDK tags. SDK tags follow the sdk-<version>.<patch> format (e.g., sdk-1.1.92.0).

This scheme was adopted following the 1.1.96 Vulkan specification release.