From 4a54ace195b3775ba5408e6f71464d924ede0237 Mon Sep 17 00:00:00 2001 From: Brian Paul Date: Thu, 20 May 2004 22:27:59 +0000 Subject: lots of updates --- docs/fbdev-dri.html | 100 +++++++++++++++++++++++++++++++++++++++++++++------- 1 file changed, 88 insertions(+), 12 deletions(-) (limited to 'docs/fbdev-dri.html') diff --git a/docs/fbdev-dri.html b/docs/fbdev-dri.html index 1c56478ca6..06277f5655 100644 --- a/docs/fbdev-dri.html +++ b/docs/fbdev-dri.html @@ -1,4 +1,4 @@ - + Mesa fbdev/DRI Environment @@ -36,16 +36,95 @@ Keith Whitwell. To use fbdev/DRI, you'll need a Linux 2.4 or 2.6 kernel.

+

Background Info

+

-The fbdev/DRI Mesa code is in the Mesa CVS trunk (to be released as Mesa -5.1 in the future). +The Mesa-based DRI drivers used to be hosted in the DRI tree (which is +basically a copy of the XFree86 tree). +Since the Mesa-based DRI drivers are moreso "Mesa drivers" than "XFree86 +drivers" and the fact that with some work, the drivers could be used +without X, the driver code was moved into the Mesa tree.

+

+So now the DRI drivers can be compiled for two different environments: +fbdev and XFree86. +To build the drivers for XFree86, one has to download/build the DRI +source tree. +Eventually, we'd like to be able to build the drivers for XFree86 outside +of the XFree86/DRI trees. +

+ + +

2. Compilation

+

2.1 Compiling the DRM modules

+ +

+First, you'll need the DRM (Direct Rendering Manager) kernel module sources. +They're found in a module of the DRI CVS tree. +To obtain the code do the following: +

+
+   cvs -d:pserver:anonymous@pdx.freedesktop.org:/cvs/dri login
+
+

+Press Enter/Return when prompted for a password. Then, +

+
+   cvs -d:pserver:anonymous@pdx.freedesktop.org:/cvs/dri co drm
+
+ +

+Compile the DRM kernel modules: +

+
+  cd drm/linux
+  make
+
+

-Assuming you're starting with a fresh Mesa CVS checkout, do the following: +Note: you may need to be root in order to make a few symlinks. +

+

+When compilation is done, you should have at least the following +kernel modules: +

+
+  gamma.o
+  i810.o
+  i830.o
+  mach64.o
+  mga.o
+  r128.o
+  radeon.o
+  savage.o
+  sis.o
+  tdfx.o
+  via.o
+
+

+You'll probably want to copy/move them into your kernel module directory +(for example: /lib/modules/2.4.18-14/kernel/drivers/char/drm/). +

+ + + +

2.2 Compiling the Mesa drivers

+ +

+Begin by editing the Mesa/configs/default file to set +the DRM_SOURCE_PATH variable. +Set it to the location where the DRM module sources are located. +For example, if your current directory in step 2.1 was /home/fred/ +set DRM_SOURCE_PATH to /home/fred/drm +

+ +

+Next, assuming you're starting with a fresh Mesa CVS checkout, +do the following: 

    make linux-solo
@@ -57,7 +136,7 @@ first to remove the old object files.
 

 
 

-When this is finished, check the Mesa/lib directory
+When this is finished, check the Mesa/lib/ directory
 to verify that the following files were made:
 

 
@@ -89,11 +168,12 @@ working from the console.
 

 
 
-
3.1 Kernel Modules

+
3.1 Load Kernel Modules

 
 

-You'll need to load kernel modules specific to your graphics hardware.
-The following kernel modules should be included with your kernel.
+You'll need to load the kernel modules specific to your graphics hardware.
+Typically, this consists of the agpgart module, an fbdev driver module
+and the DRM kernel module (from step 2.1).
 

 
 
@@ -135,10 +215,6 @@ radeonfb               21900   0  (unused)
 agpgart                43072   1
-

-If the driver complains that the radeon/mga/etc/ kernel module is too -old, you'll have to compile/install a newer one from the DRI project. -

3.2 Configuration File

-- cgit v1.2.3