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
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
Name
EXT_device_query_name
Name Strings
EGL_EXT_device_query_name
Contributors
Kyle Brenneman, NVIDIA (kbrenneman 'at' nvidia.com)
Daniel Kartch, NVIDIA (dkartch 'at' nvidia.com)
Contact
Kyle Brenneman, NVIDIA (kbrenneman 'at' nvidia.com)
Status
Complete
Version
Version 1 - June 12, 2020
Number
EGL Extension #140
Extension Type
EGL device extension
Dependencies
Written based on the wording of the EGL 1.5 specification.
EGL_EXT_device_query is required.
Overview
The EGL_EXT_device_enumeration and EGL_EXT_device_query extensions
provide a list of devices and a list of extensions, but lacks a way
to find a name for a device that an application can present to a
user.
This extension adds two new strings that an application can query to
find human-readable names.
New Types
None
New Functions
None
New Tokens
Accepted by the <name> parameter of eglQueryDeviceStringEXT:
EGL_RENDERER_EXT 0x335F
New Device Queries
eglQueryDeviceStringEXT accepts two new attributes.
EGL_VENDOR and EGL_RENDERER_EXT return a human-readable name for the
vendor and device, respectively.
The format of the EGL_VENDOR and EGL_RENDERER strings is
implementation-dependent.
The EGL_VENDOR string for an EGLDeviceEXT is not required to match
the EGL_VENDOR string for an EGLDisplay or the GL_VENDOR string for
a context. Similarly, the EGL_RENDERER string is not required to
match the GL_RENDERER string for a context.
Issues
1. Do we need a device query, instead of just creating an
EGLDisplay and calling eglQueryString?
RESOLVED: Yes, a device-level query is useful, because some
devices might not be usable with EGL_EXT_platform_device. This
is especially true on systems where different devices are
handled by different drivers.
2. If an application creates an EGLDisplay from an EGLDevice,
are the EGL_VENDOR strings required to match?
RESOLVED: No. Some implementations might not load a driver until
eglInitialize, and so might have a different or more specific
EGL_VENDOR string associated with an EGLDisplay than with an
EGLDeviceEXT. In addition, an implementation might select a
driver to use based on other parameters in
eglGetPlatformDisplay.
Revision History
#1 (June 12, 2020) Kyle Brenneman
- Initial draft
|
