On Fri, 2 Apr 2004 19:18:21 +0300
[EMAIL PROTECTED] wrote:
[snip]
> #
> # It is enabled, but a little slow. Newer versions should be somewhat
> # faster, though there are other problems in current CVS code.
> #
> # Compiler optimizations make a big difference too. Try -O3.
>
> ok, I'll try new cvs. Hmm.. what is the most newest branch? or should I use
> trunk?
Definitely. The various savage branches are long dead.
>
>
> # > How should I first help? More info about my computer and configuration?
> # Test
> # > some settings specially?
> #
> # A (relatively) slow CPU could be a bottle neck. What does /proc/cpuinfo
> # say?
>
> Look into that address, there's my cpuinfo. And look into dri folder, it's
> /proc/dri/. Does help anything, what info it gives?
Permission problems ;-)
>
> How savage_hardware(8d02), xfree, savage.ko etc talk to each other when using
> glxgears or any app? Who is talking to who..?
>
> savage_hardware(8d02) <---> savage.ko <---> xfree <--->
> /usr/X11/lib/modules/dri/savage_dri.so <---> glxgears
xfree86 <---> libGL <---> 3D driver (savage_dri.so) <------------+-> application
^-----------------------------------------------+
hardware <---> DRM (savage.ko) <---> 3D driver (savage_dri.so) <-+
But at the moment the DRM does very little so imagine a line directly
from the 3D driver to the hardware. However, that's going to change
soon.
>
> Something like this? Correct the picture?
>
> Edie
>
Felix
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
