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 references to VK_ERROR_DEVICE_LOST 

It was mistakenly called VK_DEVICE_LOST.
This commit is contained in:
Dennis Hamester 2017-05-10 20:02:28 +02:00
parent 757a1232e6
commit 0bbfaafce1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/specs/vulkan/chapters/synchronization.txt
View File

@ -973,7 +973,7 @@ with the following return codes:
| Status | Meaning
| ename:VK_SUCCESS | The fence specified by pname:fence is signaled.
| ename:VK_NOT_READY | The fence specified by pname:fence is unsignaled.
| ename:VK_DEVICE_LOST | The device has been lost. See <<devsandqueues-lost-device,Lost Device>>.
| ename:VK_ERROR_DEVICE_LOST | The device has been lost. See <<devsandqueues-lost-device,Lost Device>>.
|====
If a <<devsandqueues-submission, queue submission>> command is pending
@ -983,7 +983,7 @@ of date.
If the device has been lost (see <<devsandqueues-lost-device,Lost Device>>),
fname:vkGetFenceStatus may: return any of the above status codes.
If the device has been lost and fname:vkGetFenceStatus is called repeatedly,
it will eventually return either ename:VK_SUCCESS or ename:VK_DEVICE_LOST.
it will eventually return either ename:VK_SUCCESS or ename:VK_ERROR_DEVICE_LOST.
include::../validity/protos/vkGetFenceStatus.txt[]
@ -1079,7 +1079,7 @@ fname:vkWaitForFences returns ename:VK_SUCCESS.
If device loss occurs (see <<devsandqueues-lost-device,Lost Device>>) before
the timeout has expired, fname:vkWaitForFences must: return in finite time
with either ename:VK_SUCCESS or ename:VK_DEVICE_LOST.
with either ename:VK_SUCCESS or ename:VK_ERROR_DEVICE_LOST.
.Note
[NOTE]