blob: 5b750070ca1ff4e9503240066546a177c1aabf8b [file] [log] [blame]
Chia-I Wuada46052010-01-21 15:29:14 +08001<html>
2
3<title>Mesa EGL</title>
4
5<head><link rel="stylesheet" type="text/css" href="mesa.css"></head>
6
7<body>
8
9<h1>Mesa EGL</h1>
10
11<p>The current version of EGL in Mesa implements EGL 1.4. More information
12about EGL can be found at
Brian Paulaeff9f92010-01-21 08:13:32 -070013<a href="http://www.khronos.org/egl/" target="_parent">
14http://www.khronos.org/egl/</a>.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080015
16<p>The Mesa's implementation of EGL uses a driver architecture. The main
17library (<code>libEGL</code>) is window system neutral. It provides the EGL
18API entry points and helper functions for use by the drivers. Drivers are
19dynamically loaded by the main library and most of the EGL API calls are
20directly dispatched to the drivers.</p>
21
Chia-I Wu65e8f812010-12-25 02:45:13 +080022<p>The driver in use decides the window system to support.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080023
24<h2>Build EGL</h2>
25
26<ol>
27<li>
Chia-I Wu3418f742010-11-02 23:55:56 +080028<p>Run <code>configure</code> with the desired client APIs and enable
29the driver for your hardware. For example</p>
Chia-I Wuada46052010-01-21 15:29:14 +080030
31<pre>
Chia-I Wu8eea0502011-06-20 11:14:56 +090032 $ ./configure --enable-gles1 --enable-gles2 \
33 --with-dri-drivers=... \
34 --with-gallium-drivers=...
Chia-I Wuada46052010-01-21 15:29:14 +080035</pre>
36
Chia-I Wu8eea0502011-06-20 11:14:56 +090037<p>The main library and OpenGL is enabled by default. The first two options
38above enables <a href="opengles.html">OpenGL ES 1.x and 2.x</a>. The last two
39options enables the listed classic and and Gallium drivers respectively.</p>
Chia-I Wuc6320c52010-10-28 17:25:07 +080040
Chia-I Wuada46052010-01-21 15:29:14 +080041</li>
42
43<li>Build and install Mesa as usual.</li>
44</ol>
45
46<p>In the given example, it will build and install <code>libEGL</code>,
Chia-I Wu8eea0502011-06-20 11:14:56 +090047<code>libGL</code>, <code>libGLESv1_CM</code>, <code>libGLESv2</code>, and one
48or more EGL drivers.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080049
50<h3>Configure Options</h3>
51
52<p>There are several options that control the build of EGL at configuration
53time</p>
54
55<ul>
56<li><code>--enable-egl</code>
57
58<p>By default, EGL is enabled. When disabled, the main library and the drivers
59will not be built.</p>
60
61</li>
62
Chia-I Wua6342af2010-01-26 10:54:45 +080063<li><code>--with-egl-driver-dir</code>
64
65<p>The directory EGL drivers should be installed to. If not specified, EGL
66drivers will be installed to <code>${libdir}/egl</code>.</p>
67
68</li>
69
Chia-I Wu8eea0502011-06-20 11:14:56 +090070<li><code>--enable-gallium-egl</code>
71
72<p>Enable the optional <code>egl_gallium</code> driver.</p>
73
74</li>
75
Chia-I Wuda39d5d2010-06-17 16:07:46 +080076<li><code>--with-egl-platforms</code>
Chia-I Wuada46052010-01-21 15:29:14 +080077
Chia-I Wub365b152010-07-03 17:18:40 +080078<p>List the platforms (window systems) to support. Its argument is a comma
Chia-I Wue7424d72010-09-19 16:54:39 +080079seprated string such as <code>--with-egl-platforms=x11,drm</code>. It decides
Chia-I Wub365b152010-07-03 17:18:40 +080080the platforms a driver may support. The first listed platform is also used by
81the main library to decide the native platform: the platform the EGL native
82types such as <code>EGLNativeDisplayType</code> or
83<code>EGLNativeWindowType</code> defined for.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080084
Chia-I Wue7424d72010-09-19 16:54:39 +080085<p>The available platforms are <code>x11</code>, <code>drm</code>,
Chia-I Wuda39d5d2010-06-17 16:07:46 +080086<code>fbdev</code>, and <code>gdi</code>. The <code>gdi</code> platform can
Chia-I Wu3418f742010-11-02 23:55:56 +080087only be built with SCons. Unless for special needs, the build system should
88select the right platforms automatically.</p>
Chia-I Wu2e3c4e42010-05-07 14:13:08 +080089
90</li>
91
92<li><code>--enable-gles1</code> and <code>--enable-gles2</code>
93
Chia-I Wu65e8f812010-12-25 02:45:13 +080094<p>These options enable OpenGL ES support in OpenGL. The result is one big
95internal library that supports multiple APIs.</p>
Chia-I Wuada46052010-01-21 15:29:14 +080096
97</li>
Chia-I Wua1306f42010-01-22 15:51:51 +080098
Chia-I Wu8eea0502011-06-20 11:14:56 +090099<li><code>--enable-shared-glapi</code>
Chia-I Wuc6320c52010-10-28 17:25:07 +0800100
Chia-I Wu8eea0502011-06-20 11:14:56 +0900101<p>By default, <code>libGL</code> has its own copy of <code>libglapi</code>.
102This options makes <code>libGL</code> use the shared <code>libglapi</code>. This
103is required if applications mix OpenGL and OpenGL ES.</p>
Chia-I Wuc6320c52010-10-28 17:25:07 +0800104
105</li>
106
Chia-I Wu8eea0502011-06-20 11:14:56 +0900107<li><code>--enable-openvg</code>
Chia-I Wu3418f742010-11-02 23:55:56 +0800108
Chia-I Wu8eea0502011-06-20 11:14:56 +0900109<p>OpenVG must be explicitly enabled by this option.</p>
Chia-I Wu3418f742010-11-02 23:55:56 +0800110
111</li>
112
Chia-I Wuada46052010-01-21 15:29:14 +0800113</ul>
114
Chia-I Wuada46052010-01-21 15:29:14 +0800115<h2>Use EGL</h2>
116
Chia-I Wu411bba32010-06-11 12:47:14 +0800117<h3>Demos</h3>
Chia-I Wuada46052010-01-21 15:29:14 +0800118
Chia-I Wu411bba32010-06-11 12:47:14 +0800119<p>There are demos for the client APIs supported by EGL. They can be found in
120mesa/demos repository.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800121
122<h3>Environment Variables</h3>
123
124<p>There are several environment variables that control the behavior of EGL at
125runtime</p>
126
127<ul>
Chia-I Wu5d8646c2010-02-02 15:34:55 +0800128<li><code>EGL_DRIVERS_PATH</code>
129
130<p>By default, the main library will look for drivers in the directory where
131the drivers are installed to. This variable specifies a list of
132colon-separated directories where the main library will look for drivers, in
Chia-I Wu6fd8b6a2010-02-02 16:47:53 +0800133addition to the default directory. This variable is ignored for setuid/setgid
134binaries.</p>
Chia-I Wu5d8646c2010-02-02 15:34:55 +0800135
Chia-I Wucba77862011-01-04 00:53:19 +0800136<p>This variable is usually set to test an uninstalled build. For example, one
137may set</p>
138
139<pre>
140 $ export LD_LIBRARY_PATH=$mesa/lib
141 $ export EGL_DRIVERS_PATH=$mesa/lib/egl
142</pre>
143
144<p>to test a build without installation</p>
145
Chia-I Wu5d8646c2010-02-02 15:34:55 +0800146</li>
147
Chia-I Wuada46052010-01-21 15:29:14 +0800148<li><code>EGL_DRIVER</code>
149
Chia-I Wuc98ea262011-01-07 16:30:08 +0800150<p>This variable specifies a full path to or the name of an EGL driver. It
151forces the specified EGL driver to be loaded. It comes in handy when one wants
152to test a specific driver. This variable is ignored for setuid/setgid
153binaries.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800154
155</li>
156
Chia-I Wuda39d5d2010-06-17 16:07:46 +0800157<li><code>EGL_PLATFORM</code>
Chia-I Wuada46052010-01-21 15:29:14 +0800158
Chia-I Wub365b152010-07-03 17:18:40 +0800159<p>This variable specifies the native platform. The valid values are the same
160as those for <code>--with-egl-platforms</code>. When the variable is not set,
161the main library uses the first platform listed in
Chia-I Wu3418f742010-11-02 23:55:56 +0800162<code>--with-egl-platforms</code> as the native platform.</p>
163
164<p>Extensions like <code>EGL_MESA_drm_display</code> define new functions to
165create displays for non-native platforms. These extensions are usually used by
166applications that support non-native platforms. Setting this variable is
167probably required only for some of the demos found in mesa/demo repository.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800168
169</li>
170
171<li><code>EGL_LOG_LEVEL</code>
172
173<p>This changes the log level of the main library and the drivers. The valid
174values are: <code>debug</code>, <code>info</code>, <code>warning</code>, and
175<code>fatal</code>.</p>
176
177</li>
178
179<li><code>EGL_SOFTWARE</code>
180
181<p>For drivers that support both hardware and software rendering, setting this
182variable to true forces the use of software rendering.</p>
183
184</li>
185</ul>
186
187<h2>EGL Drivers</h2>
188
Chia-I Wuada46052010-01-21 15:29:14 +0800189<ul>
Chia-I Wu3418f742010-11-02 23:55:56 +0800190<li><code>egl_dri2</code>
191
192<p>This driver supports both <code>x11</code> and <code>drm</code> platforms.
Chia-I Wu65e8f812010-12-25 02:45:13 +0800193It functions as a DRI driver loader. For <code>x11</code> support, it talks to
194the X server directly using (XCB-)DRI2 protocol.</p>
195
196<p>This driver can share DRI drivers with <code>libGL</code>.</p>
Chia-I Wu3418f742010-11-02 23:55:56 +0800197
198</li>
199
Chia-I Wub365b152010-07-03 17:18:40 +0800200<li><code>egl_gallium</code>
Chia-I Wuada46052010-01-21 15:29:14 +0800201
Chia-I Wub365b152010-07-03 17:18:40 +0800202<p>This driver is based on Gallium3D. It supports all rendering APIs and
203hardwares supported by Gallium3D. It is the only driver that supports OpenVG.
Chia-I Wuc6320c52010-10-28 17:25:07 +0800204The supported platforms are X11, DRM, FBDEV, and GDI.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800205
Chia-I Wu65e8f812010-12-25 02:45:13 +0800206<p>This driver comes with its own hardware drivers
207(<code>pipe_&lt;hw&gt;</code>) and client API modules
208(<code>st_&lt;api&gt;</code>).</p>
209
Chia-I Wub365b152010-07-03 17:18:40 +0800210</li>
Chia-I Wuada46052010-01-21 15:29:14 +0800211
Chia-I Wuada46052010-01-21 15:29:14 +0800212<li><code>egl_glx</code>
213
214<p>This driver provides a wrapper to GLX. It uses exclusively GLX to implement
215the EGL API. It supports both direct and indirect rendering when the GLX does.
216It is accelerated when the GLX is. As such, it cannot provide functions that
217is not available in GLX or GLX extensions.</p>
218</li>
Chia-I Wuada46052010-01-21 15:29:14 +0800219</ul>
220
Chia-I Wu65e8f812010-12-25 02:45:13 +0800221<h2>Packaging</h2>
222
223<p>The ABI between the main library and its drivers are not stable. Nor is
224there a plan to stabilize it at the moment. Of the EGL drivers,
225<code>egl_gallium</code> has its own hardware drivers and client API modules.
226They are considered internal to <code>egl_gallium</code> and there is also no
227stable ABI between them. These should be kept in mind when packaging for
228distribution.</p>
229
230<p>Generally, <code>egl_dri2</code> is preferred over <code>egl_gallium</code>
231when the system already has DRI drivers. As <code>egl_gallium</code> is loaded
232before <code>egl_dri2</code> when both are available, <code>egl_gallium</code>
Chia-I Wu8eea0502011-06-20 11:14:56 +0900233is disabled by default.</p>
Chia-I Wu65e8f812010-12-25 02:45:13 +0800234
Chia-I Wuada46052010-01-21 15:29:14 +0800235<h2>Developers</h2>
236
Chia-I Wu14cbf322010-01-27 23:18:22 +0800237<p>The sources of the main library and the classic drivers can be found at
Chia-I Wu3c967a92010-01-22 16:31:43 +0800238<code>src/egl/</code>. The sources of the <code>egl</code> state tracker can
Chia-I Wu14cbf322010-01-27 23:18:22 +0800239be found at <code>src/gallium/state_trackers/egl/</code>.</p>
240
241<p>The suggested way to learn to write a EGL driver is to see how other drivers
242are written. <code>egl_glx</code> should be a good reference. It works in any
243environment that has GLX support, and it is simpler than most drivers.</p>
244
245<h3>Lifetime of Display Resources</h3>
246
247<p>Contexts and surfaces are examples of display resources. They might live
248longer than the display that creates them.</p>
249
250<p>In EGL, when a display is terminated through <code>eglTerminate</code>, all
251display resources should be destroyed. Similarly, when a thread is released
252throught <code>eglReleaseThread</code>, all current display resources should be
253released. Another way to destory or release resources is through functions
254such as <code>eglDestroySurface</code> or <code>eglMakeCurrent</code>.</p>
255
256<p>When a resource that is current to some thread is destroyed, the resource
257should not be destroyed immediately. EGL requires the resource to live until
258it is no longer current. A driver usually calls
259<code>eglIs&lt;Resource&gt;Bound</code> to check if a resource is bound
260(current) to any thread in the destroy callbacks. If it is still bound, the
261resource is not destroyed.</p>
262
263<p>The main library will mark destroyed current resources as unlinked. In a
264driver's <code>MakeCurrent</code> callback,
265<code>eglIs&lt;Resource&gt;Linked</code> can then be called to check if a newly
266released resource is linked to a display. If it is not, the last reference to
267the resource is removed and the driver should destroy the resource. But it
268should be careful here because <code>MakeCurrent</code> might be called with an
269uninitialized display.</p>
270
271<p>This is the only mechanism provided by the main library to help manage the
272resources. The drivers are responsible to the correct behavior as defined by
273EGL.</p>
Chia-I Wuada46052010-01-21 15:29:14 +0800274
Chia-I Wu1b2b08c2010-02-05 12:44:45 +0800275<h3><code>EGL_RENDER_BUFFER</code></h3>
276
277<p>In EGL, the color buffer a context should try to render to is decided by the
278binding surface. It should try to render to the front buffer if the binding
279surface has <code>EGL_RENDER_BUFFER</code> set to
280<code>EGL_SINGLE_BUFFER</code>; If the same context is later bound to a
281surface with <code>EGL_RENDER_BUFFER</code> set to
282<code>EGL_BACK_BUFFER</code>, the context should try to render to the back
283buffer. However, the context is allowed to make the final decision as to which
284color buffer it wants to or is able to render to.</p>
285
286<p>For pbuffer surfaces, the render buffer is always
287<code>EGL_BACK_BUFFER</code>. And for pixmap surfaces, the render buffer is
288always <code>EGL_SINGLE_BUFFER</code>. Unlike window surfaces, EGL spec
289requires their <code>EGL_RENDER_BUFFER</code> values to be honored. As a
290result, a driver should never set <code>EGL_PIXMAP_BIT</code> or
291<code>EGL_PBUFFER_BIT</code> bits of a config if the contexts created with the
292config won't be able to honor the <code>EGL_RENDER_BUFFER</code> of pixmap or
293pbuffer surfaces.</p>
294
295<p>It should also be noted that pixmap and pbuffer surfaces are assumed to be
296single-buffered, in that <code>eglSwapBuffers</code> has no effect on them. It
297is desirable that a driver allocates a private color buffer for each pbuffer
298surface created. If the window system the driver supports has native pbuffers,
299or if the native pixmaps have more than one color buffers, the driver should
300carefully attach the native color buffers to the EGL surfaces, re-route them if
301required.</p>
302
303<p>There is no defined behavior as to, for example, how
304<code>glDrawBuffer</code> interacts with <code>EGL_RENDER_BUFFER</code>. Right
305now, it is desired that the draw buffer in a client API be fixed for pixmap and
306pbuffer surfaces. Therefore, the driver is responsible to guarantee that the
307client API renders to the specified render buffer for pixmap and pbuffer
308surfaces.</p>
309
Chia-I Wue16f5772010-02-17 19:52:29 +0800310<h3><code>EGLDisplay</code> Mutex</h3>
311
312The <code>EGLDisplay</code> will be locked before calling any of the dispatch
313functions (well, except for GetProcAddress which does not take an
314<code>EGLDisplay</code>). This guarantees that the same dispatch function will
315not be called with the sample display at the same time. If a driver has access
316to an <code>EGLDisplay</code> without going through the EGL APIs, the driver
317should as well lock the display before using it.
318
Chia-I Wuada46052010-01-21 15:29:14 +0800319</body>
320</html>