X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=docs%2Fegl.html;h=5b750070ca1ff4e9503240066546a177c1aabf8b;hb=dd898c3e89597f841a55272be1ccc07345500f60;hp=559bd9904695e06ca1c5b3c730c6cc1427ad54b8;hpb=411bba34462b9fe7e4eb63f653b1d083ff01910d;p=mesa.git diff --git a/docs/egl.html b/docs/egl.html index 559bd990469..5b750070ca1 100644 --- a/docs/egl.html +++ b/docs/egl.html @@ -19,35 +19,33 @@ API entry points and helper functions for use by the drivers. Drivers are dynamically loaded by the main library and most of the EGL API calls are directly dispatched to the drivers.
-The driver in use decides the window system to support. For drivers that -support hardware rendering, there are usually multiple drivers supporting the -same window system. Each one of of them supports a certain range of graphics -cards.
+The driver in use decides the window system to support.
Run configure
with the desired state trackers and enable
-the Gallium driver for your hardware. For example
Run configure
with the desired client APIs and enable
+the driver for your hardware. For example
- $ ./configure --enable-gles-overlay --with-state-trackers=egl,vega --enable-gallium-{swrast,intel} + $ ./configure --enable-gles1 --enable-gles2 \ + --with-dri-drivers=... \ + --with-gallium-drivers=...-
The main library and OpenGL is enabled by default. The first option enables
-OpenGL ES 1.x and 2.x. The egl
state
-tracker is needed by a number of EGL drivers. EGL drivers will be covered
-later. The vega state tracker provides OpenVG
-1.x.
The main library and OpenGL is enabled by default. The first two options +above enables OpenGL ES 1.x and 2.x. The last two +options enables the listed classic and and Gallium drivers respectively.
+In the given example, it will build and install libEGL
,
-libGL
, libGLESv1_CM
, libGLESv2
,
-libOpenVG
, and one or more EGL drivers.
libGL
, libGLESv1_CM
, libGLESv2
, and one
+or more EGL drivers.
${libdir}/egl
.
---with-egl-displays
-
-List the window system(s) to support. It is by default x11
,
-which supports the X Window System. Its argument is a comma separated string
-like, for example, --with-egl-displays=x11,kms
. Because an EGL
-driver decides which window system to support, this example will enable two
-(sets of) EGL drivers. One supports the X window system and the other supports
-bare KMS (kernel modesetting).
--enable-gallium-egl
-The available displays are x11
, kms
,
-fbdev
, and gdi
. The gdi
display can
-only be built with SCons.
Enable the optional egl_gallium
driver.
--with-state-trackers
+--with-egl-platforms
+
+List the platforms (window systems) to support. Its argument is a comma
+seprated string such as --with-egl-platforms=x11,drm
. It decides
+the platforms a driver may support. The first listed platform is also used by
+the main library to decide the native platform: the platform the EGL native
+types such as EGLNativeDisplayType
or
+EGLNativeWindowType
defined for.
The argument is a comma separated string. It is usually used to specify the
-rendering APIs, such as OpenVG, to build. But it should be noted that a number
-of EGL drivers depend on the egl
state tracker. They will
-not be built without the egl
state tracker.
The available platforms are x11
, drm
,
+fbdev
, and gdi
. The gdi
platform can
+only be built with SCons. Unless for special needs, the build system should
+select the right platforms automatically.
--enable-gles-overlay
+--enable-gles1
and --enable-gles2
-OpenGL and OpenGL ES are not controlled by
---with-state-trackers
. OpenGL is always built. To build OpenGL
-ES, this option must be explicitly given.
These options enable OpenGL ES support in OpenGL. The result is one big +internal library that supports multiple APIs.
--enable-gles1
and --enable-gles2
+--enable-shared-glapi
-Unlike --enable-gles-overlay
, which builds one library for each
-rendering API, these options enable OpenGL ES support in OpenGL. The result is
-one big library that supports multiple APIs. This is used by DRI drivers and
-egl_dri2
EGL driver.
+
By default, libGL
has its own copy of libglapi
.
+This options makes libGL
use the shared libglapi
. This
+is required if applications mix OpenGL and OpenGL ES.
--enable-gallium-swrast
+--enable-openvg
-This option is not specific to EGL. But if there is no driver for your -hardware, or you are experiencing problems with the hardware driver, you can -enable the swrast DRM driver. It is a dummy driver and EGL will fallback to -software rendering automatically.
+OpenVG must be explicitly enabled by this option.
This variable is usually set to test an uninstalled build. For example, one +may set
+ ++ $ export LD_LIBRARY_PATH=$mesa/lib + $ export EGL_DRIVERS_PATH=$mesa/lib/egl ++ +
to test a build without installation
+EGL_DRIVER
-This variable specifies a full path to an EGL driver and it forces the -specified EGL driver to be loaded. It comes in handy when one wants to test a -specific driver. This variable is ignored for setuid/setgid binaries.
+This variable specifies a full path to or the name of an EGL driver. It +forces the specified EGL driver to be loaded. It comes in handy when one wants +to test a specific driver. This variable is ignored for setuid/setgid +binaries.
EGL_DISPLAY
+EGL_PLATFORM
-When EGL_DRIVER
is not set, the main library loads all
-EGL drivers that support a certain window system. EGL_DISPLAY
can
-be used to specify the window system and the valid values are, for example,
-x11
or kms
. When the variable is not set, the main
-library defaults the value to the first window system listed in
---with-egl-displays
at configuration time.
+
This variable specifies the native platform. The valid values are the same
+as those for --with-egl-platforms
. When the variable is not set,
+the main library uses the first platform listed in
+--with-egl-platforms
as the native platform.
Extensions like EGL_MESA_drm_display
define new functions to
+create displays for non-native platforms. These extensions are usually used by
+applications that support non-native platforms. Setting this variable is
+probably required only for some of the demos found in mesa/demo repository.
There are two categories of EGL drivers: Gallium and classic.
+egl_dri2
-Gallium EGL drivers supports all rendering APIs specified in EGL 1.4. These
-drivers depend on the egl
state tracker to build. The available
-drivers are
This driver supports both x11
and drm
platforms.
+It functions as a DRI driver loader. For x11
support, it talks to
+the X server directly using (XCB-)DRI2 protocol.
egl_<dpy>_i915
egl_<dpy>_i965
egl_<dpy>_nouveau
egl_<dpy>_radeon
egl_<dpy>_swrast
egl_<dpy>_vmwgfx
This driver can share DRI drivers with libGL
.
<dpy>
is given by --with-egl-displays
at
-configuration time. There is usually one EGL driver for each combination of
-the displays listed and the pipe drivers enabled. When the display is pure
-software or pure hardware, non-working combinations will not be built.
egl_gallium
-Classic EGL drivers, on the other hand, support only a subset of the
-available rendering APIs. They can be found under
-src/egl/drivers/
. There are 3 of them
This driver is based on Gallium3D. It supports all rendering APIs and +hardwares supported by Gallium3D. It is the only driver that supports OpenVG. +The supported platforms are X11, DRM, FBDEV, and GDI.
+ +This driver comes with its own hardware drivers
+(pipe_<hw>
) and client API modules
+(st_<api>
).
egl_glx
This driver provides a wrapper to GLX. It uses exclusively GLX to implement @@ -212,27 +216,21 @@ the EGL API. It supports both direct and indirect rendering when the GLX does. It is accelerated when the GLX is. As such, it cannot provide functions that is not available in GLX or GLX extensions.
egl_dri2
-
-This driver supports the X Window System as its window system. It functions
-as a DRI2 driver loader. Unlike egl_glx
, it has no dependency on
-libGL
. It talks to the X server directly using DRI2 protocol.
egl_dri
-
-This driver lacks maintenance and does not build. It is similiar
-to egl_dri2
in that it functions as a DRI(1) driver loader. But
-unlike egl_dri2
, it supports Linux framebuffer devices as its
-window system and supports EGL_MESA_screen_surface extension. As DRI1 drivers
-are phasing out, it might eventually be replaced by egl_dri2
.
The ABI between the main library and its drivers are not stable. Nor is
+there a plan to stabilize it at the moment. Of the EGL drivers,
+egl_gallium
has its own hardware drivers and client API modules.
+They are considered internal to egl_gallium
and there is also no
+stable ABI between them. These should be kept in mind when packaging for
+distribution.
To use the classic drivers, one must manually set EGL_DRIVER
at
-runtime.
Generally, egl_dri2
is preferred over egl_gallium
+when the system already has DRI drivers. As egl_gallium
is loaded
+before egl_dri2
when both are available, egl_gallium
+is disabled by default.
EGLDisplay
without going through the EGL APIs, the driver
should as well lock the display before using it.
-EGL_DISPLAY
loads all
-drivers and might eat too much memory.