commit | 47ed85b21d4242443444616ed9364ad425d80625 | [log] [tgz] |
---|---|---|
author | Courtney Goeltzenleuchter <courtney@LunarG.com> | Wed Mar 25 08:49:17 2015 -0600 |
committer | Chia-I Wu <olv@lunarg.com> | Thu Apr 16 17:33:26 2015 +0800 |
tree | 11886ffaf3711830aefcd66e6ce32107a2dc821e | |
parent | 1e8f3beb87a11fb56f0f4be7f75bec85a387aa0d [diff] |
xgl: Add IMAGE_LAYOUT_UNDEFINED part 1 of bug #12904: (1) What layout are images in when they are created? - Added new XGL_IMAGE_LAYOUT_UNINITIALIZED constant. This is the layout images are in right after creation. The application has to transition images to some useable layout before using the image. It can only be used as the source layout of a resource transition. An image is considered to have UNDEFINED layout in the following cases: * right after creation * if the contents of the memory backing the image has been changed by performing an operation on another resource which (partially or fully) shares the same memory backing The content of an image that is in UNDEFINED layout is considered undefined and unless the image is transitioned to another layout any operation on the image results in the content of the image to stay undefined. The application can transition any image from UNDEFINED layout to another layout anytime. Right after that the content of the image still remains undefined but subsequent operations performed on the image (e.g. clear) will have well defined results.
Version 0.8, 04 Feb 2015
This project provides open source tools for XGL Developers.
XGL is an Explicit API, enabling direct control over how GPUs actually work. No validation, shader recompilation, memory management or synchronization is done inside an XGL driver. Applications have full control and responsibility. Any errors in how XGL 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 XGL 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:
XGL 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 XGL specification is public. Until that time, this work is covered by the Khronos NDA governing the details of the XGL 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 XGL 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 XGL@LunarG.com; or if you prefer, via the GL Common mailing list: gl_common@khronos.org