commit | 89efef3507f8479a7b6d7d6148a4cf8a4e2c3190 | [log] [tgz] |
---|---|---|
author | Courtney Goeltzenleuchter <courtney@LunarG.com> | Thu Jun 25 18:01:43 2015 -0600 |
committer | Courtney Goeltzenleuchter <courtney@LunarG.com> | Wed Jul 01 21:08:13 2015 -0600 |
tree | c1bb2f91888cc1c32ca663bcef52b85d550ae5dd | |
parent | 6084aec6d371ad0f7d056ef8a93d1255eaa300a5 [diff] |
loader: Move CreateDevice to device table Discovered an issue where a layer was doing cleanup in it's DestroyDevice function but the CreateDevice was never called. This happened because the extension was only enabled on the device chain and the device chain doesn't actually call CreateDevice. That happens on the Instance chain. Making it so that we can call down the device chain - which is terminated by the ICD. We need to know the real device object to construct the device chain heiarchy and when calling down the device chain it should end with the ICD doing the actual device object creation. This patch fixes the issue by using the same process as CreateInstance. The loader will call the ICD's CreateDevice and pass that in the *pDevice argument. The layers then ignore the PhysicalDevice parameter and use the *pDevice to access the device chain. To prevent the ICD from being called twice needed to stub in a special loader_GetDeviceChainProcAddr to provide a stub for only CreateDevice as the end of the chain.
Version 0.8, 04 Feb 2015
This project provides open source tools for VK Developers.
VK is an Explicit API, enabling direct control over how GPUs actually work. No validation, shader recompilation, memory management or synchronization is done inside an VK driver. Applications have full control and responsibility. Any errors in how VK is used are likely to result in a crash. This project provides layered utility libraries to ease development and help guide developers to proven safe patterns.
New with VK in an extensible layered architecture that enables significant innovation in tools:
The components here are being shared with the Khronos community to provide insights into the specification as we approach an alpha header, and to assists those doing demos for GDC.
The following components are available:
VK Library and header files, which include:
Core Validation Layers
BUILD.md includes directions for building all the components, running the validation tests and running the demo applications.
Information on how to enable the various Debug and Validation layers is in layers/README.md.
This version of the components are written based on the following preliminary specs and proposals:
This work is intended to be released as open source under a BSD-style license once the VK specification is public. Until that time, this work is covered by the Khronos NDA governing the details of the VK API.
While this project is being developed by LunarG, Inc; there are many other companies and individuals making this possible: Valve Software, funding project development; Intel Corporation, providing full hardware specifications and valuable technical feedback; AMD, providing VK spec editor contributions; ARM, contributing a Chairman for this working group within Khronos; Nvidia, providing an initial co-editor for the spec; Qualcomm for picking up the co-editor's chair; and Khronos, for providing hosting within GitHub.
If you have questions or comments about this driver; or you would like to contribute directly to this effort, please contact us at VK@LunarG.com; or if you prefer, via the GL Common mailing list: gl_common@khronos.org