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 <h1>2. Compilation
</h1>
35 You'll need the DRM and pciaccess libraries. Check with:
38 pkg-config --modversion libdrm
39 pkg-config --modversion pciaccess
43 You can get them from the git repository with:
46 git clone git://anongit.freedesktop.org/git/mesa/drm
47 git clone git://anongit.freedesktop.org/git/xorg/lib/libpciaccess
51 See the README files in those projects for build/install instructions.
56 You'll need fbdev header files. Check with:
59 ls -l /usr/include/linux/fb.h
63 Compile Mesa with the 'linux-solo' configuration:
70 When complete you should have the following:
73 <li>lib/libGL.so - the GL library which applications link with
74 <li>lib/*_dri_so - DRI drivers
75 <li>lib/miniglx.conf - sample MiniGLX config file
76 <li>progs/miniglx/* - several MiniGLX sample programs
81 <h1>3. Using fbdev/DRI
</h1>
84 If an X server currently running, exit/stop it so you're working from
89 <h2>3.1 Load Kernel Modules
</h2>
92 You'll need to load the kernel modules specific to your graphics hardware.
93 Typically, this consists of the agpgart module, an fbdev driver module
94 and the DRM kernel module.
97 As root, the kernel modules can be loaded as follows:
101 If you have Intel i915/i945 hardware:
104 modprobe agpgart # the AGP GART module
105 modprobe intelfb # the Intel fbdev driver
106 modprobe i915 # the i915/
945 DRI kernel module
110 If you have ATI Radeon/R200 hardware:
113 modprobe agpgart # the AGP GART module
114 modprobe radeonfb # the Radeon fbdev driver
115 modprobe radeon # the Radeon DRI kernel module
119 If you have ATI Rage
128 hardware:
122 modprobe agpgart # the AGP GART module
123 modprobe aty128fb # the Rage
128 fbdev driver
124 modprobe r128 # the Rage
128 DRI kernel module
128 If you have Matrox G200/G400 hardware:
131 modprobe agpgart # the AGP GART module
132 modprobe mgafb # the Matrox fbdev driver
133 modprobe mga # the Matrox DRI kernel module
137 To verify that the agpgart, fbdev and drm modules are loaded:
140 ls -l /dev/agpgart /dev/fb* /dev/dri
143 Alternately, use lsmod to inspect the currently installed modules.
144 If you have problems, look at the output of dmesg.
148 <h2>3.2 Configuration File
</h2>
151 Copy the sample miniglx.conf to /etc/miniglx.conf and review/edit its contents.
152 Alternately, the MINIGLX_CONF environment variable can be used to
153 indicate the location of miniglx.conf
156 To determine the pciBusID value, run lspci and examine the output.
161 00:
02.0 VGA compatible controller: Intel Corporation
82915G/GV/
910GL Express Chipset Family Graphics Controller (rev
04)
164 00:
02.0 indicates that pciBusID should be PCI:
0:
2:
0
170 <h2>3.3 Running fbdev/DRI Programs
</h2>
173 Make sure your LD_LIBRARY_PATH environment variable is set to the
174 location of the libGL.so library. You may need to append other paths
175 to LD_LIBRARY_PATH if libpciaccess.so is in a non-standard location,
180 Change to the
<code>Mesa/progs/miniglx/
</code> directory and
181 start the sample_server program in the background:
184 ./sample_server
&
188 Then try running the
<code>miniglxtest
</code> program:
194 You should see a rotating quadrilateral which changes color as it rotates.
195 It will exit automatically after a bit.
199 If you run other tests in the miniglx/ directory, you may want to run
200 them from a remote shell so that you can stop them with ctrl-C.
205 <h1>4.0 Troubleshooting
</h1>
209 If you try to run miniglxtest and get the following:
212 [miniglx] failed to probe chipset
213 connect: Connection refused
214 server connection lost
216 It means that the sample_server process is not running.
223 <h1>5.0 Programming Information
</h1>
226 OpenGL/Mesa is interfaced to fbdev via the
<a href=
"MiniGLX.html">MiniGLX
</a>
228 MiniGLX is a subset of Xlib and GLX API functions which provides just
229 enough functionality to setup OpenGL rendering and respond to simple
234 Since MiniGLX is a subset of the usual Xlib and GLX APIs, programs written
235 to the MiniGLX API can also be run on full Xlib/GLX implementations.
236 This allows some degree of flexibility for software development and testing.
240 However, the MiniGLX API is not binary-compatible with full Xlib/GLX.
241 Some of the structures are different and some macros/functions work
243 See the
<code>GL/miniglx.h
</code> header file for details.