status-im
/
Vulkan-Docs
mirror of https://github.com/status-im/Vulkan-Docs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fix Note markup

This commit is contained in:
Petr Kraus 2017-12-04 20:46:27 +01:00
parent 2f5bc66d7a
commit 79a4549d0e
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/specs/vulkan/chapters/VK_KHR_android_surface/platformCreateSurface_android.txt
View File

@ -29,7 +29,7 @@ same code:ANativeWindow and any attempts to connect to the same
code:ANativeWindow through other platform mechanisms will fail. code:ANativeWindow through other platform mechanisms will fail.
[NOTE] [NOTE]
.NOTE .Note
==== ====
In particular, only one sname:VkSurfaceKHR can: exist at a time for a given In particular, only one sname:VkSurfaceKHR can: exist at a time for a given
window. window.

2
doc/specs/vulkan/chapters/features.txt
View File

@ -18,7 +18,7 @@ explicitly queried before use to ensure they are supported by the
implementation. implementation.
[NOTE] [NOTE]
.Note on extensibility .Note
==== ====
The features and limits are reported via basic structures (that is The features and limits are reported via basic structures (that is
slink:VkPhysicalDeviceFeatures and slink:VkPhysicalDeviceLimits), as well as slink:VkPhysicalDeviceFeatures and slink:VkPhysicalDeviceLimits), as well as

2
doc/specs/vulkan/chapters/resources.txt
View File

@ -3890,8 +3890,8 @@ A buffer or image memory barrier is not required to acquire _ownership_ when
no queue family owns the resource - it is implicitly acquired upon first use no queue family owns the resource - it is implicitly acquired upon first use
within a queue. within a queue.
.Note
[NOTE] [NOTE]
.Note
==== ====
Images still require a <<resources-image-layouts, layout transition>> from Images still require a <<resources-image-layouts, layout transition>> from
ename:VK_IMAGE_LAYOUT_UNDEFINED or ename:VK_IMAGE_LAYOUT_PREINITIALIZED ename:VK_IMAGE_LAYOUT_UNDEFINED or ename:VK_IMAGE_LAYOUT_PREINITIALIZED

4
doc/specs/vulkan/chapters/shaders.txt
View File

@ -278,8 +278,8 @@ The order that coherent writes to different locations become available is
undefined, unless enforced by a memory barrier instruction or other memory undefined, unless enforced by a memory barrier instruction or other memory
dependency. dependency.
.Note
[NOTE] [NOTE]
.Note
==== ====
Explicit memory dependencies must: still be used to guarantee availability Explicit memory dependencies must: still be used to guarantee availability
and visibility for access via other buffers, buffer views, or image views. and visibility for access via other buffers, buffer views, or image views.
@ -295,8 +295,8 @@ write.
Atomic operations ensure automatic availability and visibility for writes Atomic operations ensure automatic availability and visibility for writes
and reads in the same way as those to code:Coherent variables. and reads in the same way as those to code:Coherent variables.
[NOTE]
.Note .Note
[[NOTE]]
==== ====
Memory accesses performed on different resource descriptors with the same Memory accesses performed on different resource descriptors with the same
memory backing may: not be well-defined even with the code:Coherent memory backing may: not be well-defined even with the code:Coherent