Merge pull request #502 from dennishamester/fix_device_lost

Fix references to VK_ERROR_DEVICE_LOST
This commit is contained in:
Jon Leech 2017-10-18 01:54:06 -07:00 committed by GitHub
commit 07040e4b7d
1 changed files with 3 additions and 3 deletions

View File

@ -1270,7 +1270,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
@ -1280,7 +1280,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[]
--
@ -1390,7 +1390,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]