Lines Matching +full:- +full:- +full:with +full:- +full:dri +full:- +full:drivers

5 ------------
21 ------------
25 The libGL.so library defines the gl- and glX-prefixed functions needed to
26 run OpenGL programs.  OpenGL client applications should link with the
27 -lGL option to use it.
30 rendering and loading/management of hardware drivers for direct rendering.
32 When libGL.so initializes itself it uses the DRI to determine the
34 The hardware drivers are expected to be in the /usr/X11R6/lib/modules/dri/
35 directory.  Drivers are named with the convention <name>_dri.so where
39 different DRI modules directory, overriding /usr/X11R6/lib/modules/dri/.
43 When libGL.so is unable to locate appropriate hardware drivers it will
50 single-thread clients is negligible.  However, the overhead of thread
51 safety for multi-threaded clients is significant.  Each GL API call
54 DRI drivers may not be.  Please consult the documentation for a driver
69 drivers may install new OpenGL extension functions into libGL.so
73 http://oss.sgi.com/projects/ogl-sample/registry/ARB/get_proc_address.spec
75 libGL.so is also designed with flexibility such that it may be used
76 with many generations of hardware drivers to come.
82 ------------------------
85 libGL.so-compatible hardware driver.  It is not intended for end
91 libGL.so is built inside XFree86 with sources found in xc/lib/GL/.
95 	xc/lib/dri/XF86dri.c
96 	xc/lib/dri/dri_glx.c
112 The glapi_x86.X and assyntax.h files implement x86-optimized dispatch
113 of GL functions.  They are not required; C-based dispatch can be used
114 instead, with a slight performance penalty.
121 call is made to driCreateDisplay().  This function uses DRI facilities
123 display.  Each screen's driver is then opened with dlopen() and asked
138 In order to provide forward compatibility with future drivers, libGL.so
139 allows drivers to register new OpenGL extension functions which weren't
142 The register_extensions() function in xc/lib/GL/dri/dri_glx.c is called
143 as soon as libGL.so is loaded.  This is done with gcc's constructor
147 the DRI driver for each, and calls the driver's __driRegisterExtensions()
161 can't be handled correctly using a C-based solution.
184 For higher performance in the common single-thread case, the global
186 This variable will be NULL when in multi-thread mode.
192 libGL.so uses the XFree86 xthreads package to manage a thread-specific
195 Drivers may use the _glapi_set/get_context() functions to maintain
196 a private thread-specific context pointer.