blob: f18e9067c3e5a7cfbea54f7bb8ff316fc6e03a73 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
|
// Copyright 2017-2023 The Khronos Group Inc.
//
// SPDX-License-Identifier: CC-BY-4.0
include::{generated}/meta/{refprefix}VK_KHR_get_display_properties2.adoc[]
=== Other Extension Metadata
*Last Modified Date*::
2017-02-21
*IP Status*::
No known IP claims.
*Contributors*::
- Ian Elliott, Google
- James Jones, NVIDIA
=== Description
This extension provides new queries for device display properties and
capabilities that can be easily extended by other extensions, without
introducing any further queries.
This extension can be considered the `apiext:VK_KHR_display` equivalent of
the `apiext:VK_KHR_get_physical_device_properties2` extension.
include::{generated}/interfaces/VK_KHR_get_display_properties2.adoc[]
=== Issues
1) What should this extension be named?
*RESOLVED*: `VK_KHR_get_display_properties2`.
Other alternatives:
* `VK_KHR_display2`
* One extension, combined with `VK_KHR_surface_capabilites2`.
2) Should extensible input structs be added for these new functions:
*RESOLVED*:
* flink:vkGetPhysicalDeviceDisplayProperties2KHR: No.
The only current input is a slink:VkPhysicalDevice.
Other inputs would not make sense.
* flink:vkGetPhysicalDeviceDisplayPlaneProperties2KHR: No.
The only current input is a slink:VkPhysicalDevice.
Other inputs would not make sense.
* flink:vkGetDisplayModeProperties2KHR: No.
The only current inputs are a slink:VkPhysicalDevice and a
slink:VkDisplayModeKHR.
Other inputs would not make sense.
3) Should additional display query functions be extended?
*RESOLVED*:
* flink:vkGetDisplayPlaneSupportedDisplaysKHR: No.
Extensions should instead extend
flink:vkGetDisplayPlaneCapabilitiesKHR().
=== Version History
* Revision 1, 2017-02-21 (James Jones)
** Initial draft.
|
