Re: [Dri-devel] compilation questions, with apologies

[R. R. <ren...@cp...>]

Mladen Gavrilovic wrote:
> I apologize if this is not the type of thing I should be posting in this
> list, as it is not development related per se; however, I wasn't able to
> get answers to my questions in dri-users.  If this is inappropriate let
> me know and I won't post here again.
I think this is ok...
 
> That said, I'm running a Celeron 366@458 with 64 MB RAM and a Voodoo3
> 3000.  I have a few questions about compiling DRI:
> 
> 1)  The Compilation Guide says that AGP support in the kernel is "not
> required" for Voodoo3.  Does this mean that it is completely unnecessary
> with no performance loss, or that it is not ABSOLUTELY necessary but
> good to have?
It's ABSOLUTELY not necessary for a Voodoo 3/4/5, not even "good to
have" !
 
> 2)  In editing the hosts.def file I'deleted the following lines:
> 
> #define DefaultGcc2AxpOpt -O2 -mcpu=ev6
> ...
> #ifdef AlphaArchitecture
> #define LibraryCDebugFlags -O2 -mcpu=ev6
> #else
> <I left the next line in since it is the default for non-Alpha>
> #endif
> ...
> #ifdef i386Architecture
> #define MesaUse3DNow YES
> #if HasKatmaiSupport
> #  define MesaUseKatmai YES
> #endif
> #endif
> 
> Any problem with cutting any of this out (using a Celeron with no
> 3DNow or SSE)?
Should be ok (but you don't need to delete those)...
 
> 3)  I changed the line that used to be something like:
> 
> #define XF86CardDrivers vga tdfx mga ati i810 glint, etc.
> 
> to:
> 
> #define XF86CardDrivers tdfx
> 
> since I don't want anything but what is necessary for a Voodoo3 to
> compile.  Is this OK?
Yep. I'd recommend leaving "vga" in, because if you have trouble with
tdfx, you could at least start with standard vga mode... but it
wouldn'tz be very useful and tdfx will MOST LIKELY cause no trouble at
all ;-) !
 
> 4)  Is there any reason that the kernel modules must be built separately
> with "make -f Makefile.linux"?  If I force module compilation in
> hosts.def, all modules are built (despite the above CardDrivers line).
> The same thing happens if the modules are not built and I type in the
> make command by hand.  Is there any difference between the two?
No. The result is the same. It#s just that if you didn't force them to
be built (in host.def) you need to do it explicitly. Another option is
to use the DRM from Kernel 2.4.2, which works fine for me ony ma V5 5500
AGP !

> 5)  Finally, when all is finished and the modules built, I end up with
> two tdfx modules:  tdfx.o and tdfx_drv.o.  The first one, tdfx.o, is
> familiar... but what is tdfx_drv.o?
You have to INSTALL the whole build tree after it using "make install"
(as described in the complitaion guide). tdfx_drv.o is then installed in
/usr/X11R6/lib/modules/drivers and tdfx_dri.so is installed in
/usr/X11R6/lib/modules/dri.

The kernel module needs to be manually installed to
/lib/modules/<kernel_version>/char or called directly via insmod
<path_to_tdfx.o> !

Hope this helps, 

Rene
-- 
R. Reucher                     voice:  +49/621/4803-174
COMPAREX GmbH, VSSS            fax:    +49/621/4803-141
Mannheimerstr. 105             e-mail: ren...@cp...
D-68535 Edingen-Neckarhausen