• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1Name
2
3    EXT_device_query_name
4
5Name Strings
6
7    EGL_EXT_device_query_name
8
9Contributors
10
11    Kyle Brenneman,  NVIDIA  (kbrenneman 'at' nvidia.com)
12    Daniel Kartch, NVIDIA (dkartch 'at' nvidia.com)
13
14Contact
15
16    Kyle Brenneman,  NVIDIA  (kbrenneman 'at' nvidia.com)
17
18Status
19
20    Complete
21
22Version
23
24    Version 1 - June 12, 2020
25
26Number
27
28    EGL Extension #140
29
30Extension Type
31
32    EGL device extension
33
34Dependencies
35
36    Written based on the wording of the EGL 1.5 specification.
37
38    EGL_EXT_device_query is required.
39
40Overview
41
42    The EGL_EXT_device_enumeration and EGL_EXT_device_query extensions
43    provide a list of devices and a list of extensions, but lacks a way
44    to find a name for a device that an application can present to a
45    user.
46
47    This extension adds two new strings that an application can query to
48    find human-readable names.
49
50New Types
51
52    None
53
54New Functions
55
56    None
57
58New Tokens
59
60    Accepted by the <name> parameter of eglQueryDeviceStringEXT:
61
62        EGL_RENDERER_EXT                0x335F
63
64New Device Queries
65
66    eglQueryDeviceStringEXT accepts two new attributes.
67
68    EGL_VENDOR and EGL_RENDERER_EXT return a human-readable name for the
69    vendor and device, respectively.
70
71    The format of the EGL_VENDOR and EGL_RENDERER strings is
72    implementation-dependent.
73
74    The EGL_VENDOR string for an EGLDeviceEXT is not required to match
75    the EGL_VENDOR string for an EGLDisplay or the GL_VENDOR string for
76    a context. Similarly, the EGL_RENDERER string is not required to
77    match the GL_RENDERER string for a context.
78
79Issues
80
81    1.  Do we need a device query, instead of just creating an
82        EGLDisplay and calling eglQueryString?
83
84        RESOLVED: Yes, a device-level query is useful, because some
85        devices might not be usable with EGL_EXT_platform_device. This
86        is especially true on systems where different devices are
87        handled by different drivers.
88
89    2.  If an application creates an EGLDisplay from an EGLDevice,
90        are the EGL_VENDOR strings required to match?
91
92        RESOLVED: No. Some implementations might not load a driver until
93        eglInitialize, and so might have a different or more specific
94        EGL_VENDOR string associated with an EGLDisplay than with an
95        EGLDeviceEXT. In addition, an implementation might select a
96        driver to use based on other parameters in
97        eglGetPlatformDisplay.
98
99Revision History
100
101    #1 (June 12, 2020) Kyle Brenneman
102
103        - Initial draft
104
105