info: Add support for VK_KHR_display#1196
Conversation
|
CI Vulkan-Tools build queued with queue ID 616266. |
1 similar comment
|
CI Vulkan-Tools build queued with queue ID 616266. |
|
Example output (displays are attached to GPU1). json output is not changed because this isn't part of the schema |
f4c2de3 to
5b17eed
Compare
|
CI Vulkan-Tools build queued with queue ID 616284. |
1 similar comment
|
CI Vulkan-Tools build queued with queue ID 616284. |
5b17eed to
b594b53
Compare
|
CI Vulkan-Tools build # 1907 running. |
|
CI Vulkan-Tools build # 1907 failed. |
b594b53 to
ae8549a
Compare
|
CI Vulkan-Tools build queued with queue ID 616373. |
|
CI Vulkan-Tools build # 1910 running. |
|
CI Vulkan-Tools build # 1910 failed. |
ae8549a to
f505d06
Compare
|
CI Vulkan-Tools build queued with queue ID 616548. |
1 similar comment
|
CI Vulkan-Tools build queued with queue ID 616548. |
|
CI Vulkan-Tools build # 1911 running. |
|
CI Vulkan-Tools build # 1911 failed. |
f505d06 to
47c5aba
Compare
|
CI Vulkan-Tools build queued with queue ID 617094. |
|
CI Vulkan-Tools build queued with queue ID 617109. |
|
CI Vulkan-Tools build # 1913 running. |
|
CI Vulkan-Tools build # 1913 passed. |
This prints the results of vkGetPhysicalDeviceDisplayPropertiesKHR(), vkGetPhysicalDeviceDisplayPlanePropertiesKHR() and other related property lookups. It does not provide support to create a VK_KHR_display surface and query it. It also does not try to use VK_EXT_direct_mode_display to take control of the display from the window system.
47c5aba to
f837892
Compare
|
CI Vulkan-Tools build queued with queue ID 617175. |
1 similar comment
|
CI Vulkan-Tools build queued with queue ID 617175. |
|
CI Vulkan-Tools build # 1914 running. |
|
CI Vulkan-Tools build # 1914 passed. |
charles-lunarg
left a comment
There was a problem hiding this comment.
PR looks reasonable. I did run it locally and got a reasonable output for zero supported displays, which is good.
This prints the results of vkGetPhysicalDeviceDisplayPropertiesKHR(), vkGetPhysicalDeviceDisplayPlanePropertiesKHR() and other related property lookups.
It does not provide support to create a VK_KHR_display surface and query it.
It also does not try to use VK_EXT_direct_mode_display to take control of the display from the window system.