| commit | 5aa2763f1d0a436644207f3ab56f40cfbf9bb760 | [log] [tgz] |
|---|---|---|
| author | John Bauman <jbauman@google.com> | Fri Apr 26 12:35:52 2019 -0700 |
| committer | John Bauman <jbauman@google.com> | Fri Apr 26 16:43:51 2019 -0700 |
| tree | e55f520f42ddfa1aebdd44fec41359a2300183a3 | |
| parent | 62e58ed31dc9711381fbe80817a89b51e9ff0686 [diff] |
Add buffer creation support to VK_FUCHSIA_buffer_collection On current systems any VMO can be imported as a buffer and it will work just like a vulkan-created buffer, except that the client that doesn't use vulkan has no idea whether cache operations are needed. However on non-UMA systems it's possible that an arbitrary VMO could only be imported in very limited ways, e.g. not attachable to a vertex buffer or uniform buffer. The sysmem interface supports creating buffer collections that aren't 2D images, but are linear memory. We can extend the Vulkan buffer collection interface to allow clients to request that. The main differences between the buffer and image constraints interfaces (besides the VkBufferCreateInfo parameter) are that VkFormatFeatureFlags can be specified to require that certain operations (like VK_FORMAT_FEATURE_STORAGE_TEXEL_BUFFER_ATOMIC_BIT) are supported. and the minimum number of buffers in the collection are specified. The image interface will be extended to support those features in the future. Also updated Vulkan-Docs.diff to match the current versions: Vulkan-Docs 3c0abef815a9ffe3d1b728bb383f132543e721b1 Vulkan-Hpp b4080fb4254dbc38fef7f71a262a08fe01cd964a Change-Id: I76822922f646a5fdccd37b11f073b8555c17cd1e
This repository has been deprecated. It will continue to exist as a read-only repository servicing existing projects. Any projects utilizing this repository should be migrated to use the follow-on repositories listed below. All issues have been migrated to the new repositories.
The four new repositories are:
Repository Maintainers, May 13, 2018
Contact: mark@lunarg.com
Original README.md contents follow.
This project provides the Khronos official Vulkan ICD desktop loader and the Vulkan validation layers for Windows, Linux, Android, and MacOS.
| Platform | Build Status |
|---|---|
| Linux/Android |  |
| Windows |
Vulkan is an Explicit API, enabling direct control over how GPUs actually work. By design, minimal error checking is done inside a Vulkan driver. Applications have full control and responsibility for correct operation. Any errors in how Vulkan is used can result in a crash. This project provides Vulkan validation layers that can be enabled to assist development by enabling developers to verify their applications correct use of the Vulkan API.
Vulkan supports multiple GPUs and multiple global contexts (VkInstance). The ICD loader is necessary to support multiple GPUs and VkInstance-level Vulkan commands. Additionally, the loader manages inserting Vulkan layer libraries such as validation layers between the application and the ICD.
The following components are available in this repository:
Please see the CONTRIBUTING.md file in this repository for more details. Please see the GOVERNANCE.md file in this repository for repository management details.
BUILD.md Includes directions for building all components as well as running validation tests and demo applications.
Information on how to enable the various Validation layers is in layers/README.md.
Architecture and interface information for the loader is in loader/LoaderAndLayerInterface.md.
This work is released as open source under a Apache-style license from Khronos including a Khronos copyright.
See COPYRIGHT.txt for a full list of licenses used in this repository.
While this project has been developed primarily by LunarG, Inc., there are many other companies and individuals making this possible: Valve Corporation, funding project development; Google providing significant contributions to the validation layers; Khronos providing oversight and hosting of the project.