Hi George, On Sat, Jan 31, 2004 at 03:07:37PM +0100, George Lengel wrote:
> My questions. > At http://dri.sourceforge.net/doc/DRIcompile.html it seems to imply in order > to compile the DRI stuff, I need to compile my kernel. What is the reason for > this? Is it simply to ensure the kernel has certain things loaded? No, this is not usually necessary. Most modern kernels have the necessary support (agpgart, mtrr, etc) already included. You will need to compile the DRM modules against your current kernel though. Make sure you use the same compiler as your kernel was built with, or you will have problems. (You can usually find that out from the top of dmesg.) > Also, in reading the mail list, it seems implied that I have to compile XFree > in order to use a DRI module. Is this also absolutely necessary? Is running > the 4.3.99 binary good enough? Right now all I have pulled from CVS is the > savage branch. That should be fine. Pull Mesa and xc from DRI CVS, edit xc/config/cf/host.def to point to the Mesa directory, and in xc/Makefile comment out this line: $(MAKE_CMD) $(MFLAGS) $(WORLDOPTS) World Then you can build the drivers separately wherever they reside in the tree: xc/programs/Xserver/hw/xfree86/drivers for the 2D driver xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel for the DRM-modules xc/lib/GL/mesa/drivers/dri for the Mesa hardware support modules That should get you started. Note that I don't have any experience with the savage driver but this is what I use for other DRI work. If you have any other questions feel free to post here. -- Ryan Underwood, <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
