| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/ |
| D | READMEVK.adoc | 8 = Vulkan^(R)^ API Documentation Project
10 The link:https://github.com/KhronosGroup/Vulkan-Docs[Vulkan-Docs]
12 contains sources for the formal documentation of the Vulkan
16 * The Vulkan API Specification
20 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers])
21 * Vulkan header files (also mirrored at
22 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers])
26 link:https://github.com/KhronosGroup/Vulkan-Docs/[Vulkan-Docs].
32 …roup/Vulkan-Web-Registry/blob/main/Vulkan-Projects.adoc[Vulkan-Projects] list on the link:https://…
35 The Vulkan-Docs repository also includes the sources for the Vulkan SC
[all …]
|
| D | READMESC.adoc | 8 = Vulkan^(R)^ SC API Documentation Project
12 contains sources for the formal documentation of the Vulkan SC
16 * The Vulkan SC API Specification
20 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers] under the `sc_main` branch)
21 * Vulkan SC header files (also mirrored at
22 link:https://github.com/KhronosGroup/Vulkan-Headers[Vulkan-Headers] under the `sc_main` branch)
31 Questions and feedback on the Vulkan SC specification can be made using the GitHub
39 For standard Vulkan (not Vulkan SC) related issues, consult the
40 …roup/Vulkan-Web-Registry/blob/main/Vulkan-Projects.adoc[Vulkan-Projects] list on the link:https://…
50 many parts of the Specification at once, is difficult for the Vulkan SC Working
[all …]
|
| D | README.adoc | 8 = Vulkan^(R)^ and Vulkan^(R)^ SC API Documentation Project
10 For Vulkan^(R)^ API specific documentation see link:READMEVK.adoc[READMEVK.adoc]
12 For Vulkan^(R)^ SC API specific documentation see link:READMESC.adoc[READMESC.adoc]
20 READMESC.adoc Readme for the Vulkan SC specification
21 READMEVK.adoc Readme for the Vulkan specification
27 ChangeLog.adoc Change log summary for each public Vulkan spec update
28 ChangeLogSC.adoc Change log summary for each public Vulkan SC spec update
37 style/ Sources for "styleguide" (Vulkan Documentation and Extensions: Procedures and…
38 xml/ XML API Registry (`vk.xml`) as well as XML for non-Vulkan
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_KHR_portability_subset.adoc | 26 Vulkan implementation to be built on top of another non-Vulkan graphics API,
28 fully-conformant native Vulkan implementation.
30 This extension provides Vulkan implementations with the ability to mark
34 platforms where Vulkan is not natively supported.
37 capabilities which are required to be supported by a fully-conformant Vulkan
38 1.0 implementation, but may be optional for an implementation of the Vulkan
42 of the Vulkan 1.0 Portability Subset, and not on conformant implementations
43 of Vulkan 1.0.
44 Fully-conformant Vulkan implementations provide all the required
47 implementation is likely not fully conformant with the Vulkan spec.
[all …]
|
| D | VK_NV_external_memory.adoc | 19 Applications may wish to export memory to other Vulkan instances or other
20 APIs, or import memory from other Vulkan instances or other APIs to enable
21 Vulkan workloads to be split up across application module, process, or API
23 This extension enables applications to create exportable Vulkan memory
25 Vulkan instance that created them.
38 specific support usage within Vulkan for imported native memory objects, or
42 layout transitions compatible with non-Vulkan APIs, or with other instances
43 of the same Vulkan driver?
46 Separate instances of the same Vulkan driver running on the same GPU should
50 Other APIs will fall into two categories: Those that are Vulkan compatible
[all …]
|
| D | VK_EXT_pipeline_properties.adoc | 21 Vulkan SC requires offline compilation of pipelines.
26 One method of developing a Vulkan SC application is to author a Vulkan
33 compiler, the Vulkan SC application can then use this
34 pname:pipelineIdentifier for identifying the pipeline via Vulkan SC's
37 This extension allows the Vulkan application to query the
39 application can store this with its pipeline metadata and the Vulkan SC
40 application will then use to map the same state to an entry in the Vulkan SC
45 for it in native Vulkan drivers as well.
50 (1) This extension does not make sense on a strict Vulkan SC implementation.
51 It may however be of potential use in a non-strict Vulkan SC implementation.
[all …]
|
| D | vulkanscdeviations.adoc | 7 = Vulkan SC Deviations From Base Vulkan
10 The following extensions have been added to Vulkan SC:
21 The following items have been added to Vulkan SC:
36 The following aspects of Base Vulkan have been modified for Vulkan SC:
63 The following functionality has been removed from Base Vulkan in Vulkan SC:
93 Vulkan SC supports a subset of the extensions supported in Base Vulkan.
110 additional functionality in a Vulkan SC implementation beyond what is
113 implementation that exposes additional Vulkan extensions and tools support
114 but is non-conformant to the Vulkan SC specification.
116 A Vulkan SC conformant implementation with this additional functionality
[all …]
|
| D | VK_ANDROID_external_memory_android_hardware_buffer.adoc | 26 basetype:AHardwareBuffer objects created outside of the Vulkan device into
27 Vulkan memory objects, where they can: be bound to images and buffers.
28 It also allows exporting an basetype:AHardwareBuffer from a Vulkan memory
30 But since not all basetype:AHardwareBuffer usages and formats have Vulkan
31 equivalents, exporting from Vulkan provides strictly less functionality than
35 formats_ that may: not correspond to Vulkan formats.
59 image may depend on native usage flags that do not have corresponding Vulkan
69 internally is performed by a separate HAL, not the Vulkan implementation
80 to Vulkan could get the same output given the same input.
83 to Vulkan's requirements.
[all …]
|
| D | versions.adoc | 10 New minor versions of the Vulkan API are defined periodically by the Khronos
11 Vulkan Working Group.
32 [open,refpage='VK_VERSION_1_3',desc='Vulkan version 1.3',type='feature',anchor='versions-1.3',xrefs…
34 Vulkan Version 1.3 <<extendingvulkan-compatibility-promotion,promoted>> a
40 Vulkan 1.3 functionality are summarized in the <<versions-1.3-promotions,
41 Vulkan 1.3 specification appendix>>.
49 Vulkan Version 1.3 <<extendingvulkan-compatibility-promotion,promoted>> a
55 Vulkan 1.3 functionality are summarized below.
60 all formats defined by it are optional in Vulkan 1.3.
67 `apiext:VK_EXT_extended_dynamic_state` are required in Vulkan 1.3.
[all …]
|
| D | VK_EXT_metal_objects.adoc | 19 In a Vulkan implementation that is layered on top of Metal on Apple device
21 underlying Metal objects associated with specific Vulkan objects.
24 https://github.com/KhronosGroup/Vulkan-Docs/tree/main/proposals/VK_EXT_metal_objects.adoc[extension
25 proposal document], this extension adds one new Vulkan command,
27 Vulkan objects, and supports importing the appropriate existing Metal
28 objects when creating Vulkan objects of types slink:VkDeviceMemory,
44 ** Incorporated feedback from review by the Vulkan Working Group.
|
| D | VK_NV_external_memory_win32.adoc | 19 Applications may wish to export memory to other Vulkan instances or other
20 APIs, or import memory from other Vulkan instances or other APIs to enable
21 Vulkan workloads to be split up across application module, process, or API
24 Vulkan memory objects such that the underlying resources can be referenced
25 outside the Vulkan instance that created them, and import win32 handles
26 created in the Direct3D API to Vulkan memory objects.
39 specific support usage within Vulkan for imported native memory objects, or
43 layout transitions compatible with non-Vulkan APIs, or with other instances
44 of the same Vulkan driver?
47 Separate instances of the same Vulkan driver running on the same GPU should
[all …]
|
| D | VK_KHR_maintenance3.adoc | 12 - Promoted to Vulkan 1.1 Core
19 intentionally left out or overlooked from the original Vulkan 1.0 release.
26 set, which cannot be expressed in terms of the limits in Vulkan 1.0.
31 === Promotion to Vulkan 1.1
33 All functionality in this extension is included in core Vulkan 1.1, with the
|
| D | VK_KHR_shader_atomic_int64.adoc | 12 - Promoted to Vulkan 1.2 Core
24 This extension advertises the SPIR-V *Int64Atomics* capability for Vulkan,
31 === Promotion to Vulkan 1.2
33 All functionality in this extension is included in core Vulkan 1.2, with the
35 However, if Vulkan 1.2 is supported and this extension is not, the
|
| D | VK_KHR_get_memory_requirements2.adoc | 14 - Promoted to Vulkan 1.1 Core
25 The Vulkan 1.0 slink:VkMemoryRequirements and
32 core Vulkan 1.0.
34 === Promotion to Vulkan 1.1
36 All functionality in this extension is included in core Vulkan 1.1, with the
|
| D | VK_KHR_external_memory.adoc | 16 - Promoted to Vulkan 1.1 Core
32 An application may wish to reference device memory in multiple Vulkan
35 This extension enables an application to export non-Vulkan handles from
36 Vulkan memory objects such that the underlying resources can be referenced
37 outside the scope of the Vulkan logical device that created them.
39 === Promotion to Vulkan 1.1
41 All functionality in this extension is included in core Vulkan 1.1, with the
51 Vulkan instance boundaries?
65 Further, the pipeline cache UUID was specific to Vulkan, but correlation
75 resources when using memory across multiple Vulkan instances or other APIs.
[all …]
|
| D | VK_KHR_storage_buffer_storage_class.adoc | 16 - Promoted to Vulkan 1.1 Core
23 This extension adds support for the following SPIR-V extension in Vulkan:
31 === Promotion to Vulkan 1.1
33 All functionality in this extension is included in core Vulkan 1.1.
|
| D | VK_KHR_vulkan_memory_model.adoc | 14 - Promoted to Vulkan 1.2 Core
31 The <<memory-model,Vulkan Memory Model>> formally defines how to synchronize
44 === Promotion to Vulkan 1.2
46 All functionality in this extension is included in core Vulkan 1.2, with the
48 However, if Vulkan 1.2 is supported and this extension is not, the
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/antora/modules/proposals/pages/ |
| D | index.adoc | 4 = Vulkan Proposals Start Page
6 These documents describe the Vulkan Roadmap, the Vulkan 2022 Profile
11 This is modules/proposals/pages/index.adoc in the Vulkan 'spec' antora tree.
14 This is a crosslink to the xref:spec::index.adoc[Vulkan Specification] main
18 Extensions] page in the Vulkan Guide.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | introduction.adoc | 10 ifdef::VKSC_VERSION_1_0["`Vulkan SC Specification`", ]
11 "`Vulkan Specification`" or just the "`Specification`" hereafter, describes
12 the Vulkan
16 "`Base Vulkan Specification`" refers to the Vulkan Specification
17 (https://registry.khronos.org/vulkan/) that Vulkan SC is based on.
18 "`Vulkan`" and "`Vulkan SC`" refer to the Vulkan SC API and "`Base Vulkan`"
19 refers to the Vulkan API that Vulkan SC is based on.
21 Vulkan is a http://www.open-std.org/jtc1/sc22/wg14/www/standards[C99] API
27 https://registry.khronos.org/vulkan/[Vulkan Registry]
29 The source files used to generate the Vulkan specification are stored in the
[all …]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/antora/modules/ROOT/pages/ |
| D | index.adoc | 4 = Vulkan Documentation
12 Vulkan documents including specifications, guides, tutorials and samples
15 for developing Vulkan-based applications.
17 For more details about and resources for using the Vulkan graphics API,
18 see the Vulkan developer website at https://vulkan.org .
20 This build of the site includes the Vulkan {SPECREVISION} API specification
43 link:https://github.com/KhronosGroup/Vulkan-Site/[Vulkan-Site]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/style/ |
| D | introduction.adoc | 9 specifications for new Vulkan APIs, extensions and layers, or related
11 contributing to existing Vulkan specifications.
23 This document is now formally voted on and approved by the Vulkan Working
28 changes must be made through the normal Vulkan Working Group processes.
36 and by the Vulkan Specification in the "`Terminology`" section.
45 names of Vulkan identifiers of all types.
47 creating formal Vulkan extensions and layers.
61 Vulkan Documentation is primarily written in Asciidoctor, a text markup
82 However, because of the use of custom Ruby macros in the Vulkan
114 Khronos Vulkan Working Group.
[all …]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/tests/ |
| D | README.adoc | 9 = Vulkan^(R)^ API Header Tests
12 (../.gitlab-ci.yml) for the Vulkan C headers generated here, and the
13 Vulkan-Hpp C++ headers generated by that project:
16 * htest.c - test C headers, including all Vulkan platform headers
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_EXT_external_memory_acquire_unmodified.adoc | 35 then in some Vulkan implementations
38 Note that, in some Vulkan implementations,
48 is independent of Vulkan operations such as image layout transitions, shader
56 The performance problem is due to the Vulkan implementation's need to maintain
63 then, when the application re-acquires ownership, the Vulkan implementation
69 memory remained unmodified, then the Vulkan implementation must _still_
72 If the application had the ability to inform that Vulkan implementation that
82 the image's external memory, but cannot inform the Vulkan implementation
83 of its unmodified status due to lack of Vulkan API.
84 The Vulkan implementation must perform the unnecessary data synchronization
[all …]
|
| D | VK_EXT_primitives_generated_query.adoc | 10 This proposal regards layering OpenGL over Vulkan, and provides a convenience
17 There is no direct equivalent in Vulkan.
20 query on top of Vulkan.
24 === Emulation Through Other Vulkan Queries
26 In Vulkan, the second result from the
38 `GL_CLIPPING_INPUT_PRIMITIVES_ARB` through the same Vulkan query creates
40 at a time in Vulkan.
44 A new Vulkan query type can be introduced to provide identical results to
49 stated by the Vulkan spec, if `rasterizerDiscardEnable` is enabled the query
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_QNX_external_memory_screen_buffer/ |
| D | qnx_screen_buffer.adoc | 15 objects for access via Vulkan.
24 image may depend on native usage flags that do not have corresponding Vulkan
33 used in various Vulkan interfaces are ones created explicitly with QNX
39 Therefore, during the host execution of a Vulkan command that has a QNX
45 Vulkan implementation, the buffer object should: have a
49 The exact Screen-native usage flags required depends on the Vulkan
53 the Vulkan specification.
59 formats, layouts, color models, etc., which do not have Vulkan equivalents.
62 Vulkan can: import QNX Screen buffers that have external formats, but since
74 <<memory-external-qnx-screen-buffer-formats,equivalent Vulkan format>> to
[all …]
|