3 <TITLE>Mesa fbdev/DRI Environment
</TITLE>
5 <link rel=
"stylesheet" type=
"text/css" href=
"mesa.css"></head>
9 <center><H1>Mesa fbdev/DRI Drivers
</H1></center>
12 <H1>1. Introduction
</H1>
15 The fbdev/DRI environment supports hardware-accelerated
3D rendering without
16 the X window system. This is typically used for embedded applications.
20 Contributors to this project include Jon Smirl, Keith Whitwell and Dave Airlie.
24 Applications in the fbdev/DRI environment use
25 the
<a href=
"MiniGXL.html"> MiniGLX
</a> interface to choose pixel
26 formats, create rendering contexts, etc. It's a subset of the GLX and
27 Xlib interfaces allowing some degree of application portability between
28 the X and X-less environments.
32 Some of the files needed for building this configuration are not included
33 in the normal Mesa releases so you'll need to get the latest sources
34 sources from the
<a href=
"repository.html">git repository
</a>.
38 <h1>2. Compilation
</h1>
41 You'll need the DRM and pciaccess libraries. Check with:
44 pkg-config --modversion libdrm
45 pkg-config --modversion pciaccess
49 You can get them from the git repository with:
52 git clone git://anongit.freedesktop.org/git/mesa/drm
53 git clone git://anongit.freedesktop.org/git/xorg/lib/libpciaccess
57 See the README files in those projects for build/install instructions.
62 You'll need fbdev header files. Check with:
65 ls -l /usr/include/linux/fb.h
69 Compile Mesa with the 'linux-solo' configuration:
76 When complete you should have the following:
79 <li>lib/libGL.so - the GL library which applications link with
80 <li>lib/*_dri_so - DRI drivers
81 <li>lib/miniglx.conf - sample MiniGLX config file
82 <li>progs/miniglx/* - several MiniGLX sample programs
87 <h1>3. Using fbdev/DRI
</h1>
90 If an X server currently running, exit/stop it so you're working from
95 <h2>3.1 Load Kernel Modules
</h2>
98 You'll need to load the kernel modules specific to your graphics hardware.
99 Typically, this consists of the agpgart module, an fbdev driver module
100 and the DRM kernel module.
103 As root, the kernel modules can be loaded as follows:
107 If you have Intel i915/i945 hardware:
110 modprobe agpgart # the AGP GART module
111 modprobe intelfb # the Intel fbdev driver
112 modprobe i915 # the i915/
945 DRI kernel module
116 If you have ATI Radeon/R200 hardware:
119 modprobe agpgart # the AGP GART module
120 modprobe radeonfb # the Radeon fbdev driver
121 modprobe radeon # the Radeon DRI kernel module
125 If you have ATI Rage
128 hardware:
128 modprobe agpgart # the AGP GART module
129 modprobe aty128fb # the Rage
128 fbdev driver
130 modprobe r128 # the Rage
128 DRI kernel module
134 If you have Matrox G200/G400 hardware:
137 modprobe agpgart # the AGP GART module
138 modprobe mgafb # the Matrox fbdev driver
139 modprobe mga # the Matrox DRI kernel module
143 To verify that the agpgart, fbdev and drm modules are loaded:
146 ls -l /dev/agpgart /dev/fb* /dev/dri
149 Alternately, use lsmod to inspect the currently installed modules.
150 If you have problems, look at the output of dmesg.
154 <h2>3.2 Configuration File
</h2>
157 Copy the sample miniglx.conf to /etc/miniglx.conf and review/edit its contents.
158 Alternately, the MINIGLX_CONF environment variable can be used to
159 indicate the location of miniglx.conf
162 To determine the pciBusID value, run lspci and examine the output.
167 00:
02.0 VGA compatible controller: Intel Corporation
82915G/GV/
910GL Express Chipset Family Graphics Controller (rev
04)
170 00:
02.0 indicates that pciBusID should be PCI:
0:
2:
0
176 <h2>3.3 Running fbdev/DRI Programs
</h2>
179 Make sure your LD_LIBRARY_PATH environment variable is set to the
180 location of the libGL.so library. You may need to append other paths
181 to LD_LIBRARY_PATH if libpciaccess.so is in a non-standard location,
186 Change to the
<code>Mesa/progs/miniglx/
</code> directory and
187 start the sample_server program in the background:
190 ./sample_server
&
194 Then try running the
<code>miniglxtest
</code> program:
200 You should see a rotating quadrilateral which changes color as it rotates.
201 It will exit automatically after a bit.
205 If you run other tests in the miniglx/ directory, you may want to run
206 them from a remote shell so that you can stop them with ctrl-C.
211 <h1>4.0 Troubleshooting
</h1>
215 If you try to run miniglxtest and get the following:
218 [miniglx] failed to probe chipset
219 connect: Connection refused
220 server connection lost
222 It means that the sample_server process is not running.
229 <h1>5.0 Programming Information
</h1>
232 OpenGL/Mesa is interfaced to fbdev via the
<a href=
"MiniGLX.html">MiniGLX
</a>
234 MiniGLX is a subset of Xlib and GLX API functions which provides just
235 enough functionality to setup OpenGL rendering and respond to simple
240 Since MiniGLX is a subset of the usual Xlib and GLX APIs, programs written
241 to the MiniGLX API can also be run on full Xlib/GLX implementations.
242 This allows some degree of flexibility for software development and testing.
246 However, the MiniGLX API is not binary-compatible with full Xlib/GLX.
247 Some of the structures are different and some macros/functions work
249 See the
<code>GL/miniglx.h
</code> header file for details.