On Samstag, 6. April 2002 :04, Brian Paul wrote:
> Dieter N�tzel wrote:
> > Brain wrote:
> > > Dieter N�tzel wrote:
> > > > On Wednesday, March 2002-04-03 22:05:47, Brian Paul wrote:
> > > > > -- Dieter N=FCtzel wrote:
> > > > > > =20
> > > > > > One more:
> > > > > > Brian, is the latest Mesa-4.0.2 stuff already merged?
> > > > >
> > > > > The trunk is has the latest 4.0.2 code now.
> > > >
> > > > Sorry Brian,
> > > >
> > > > but after your update the tdfx driver (V5) sigfaults during the
> > > > "texdown" demo. I verified it with the former tree. It works there.
[-]
> I've fixed this problem. Update your tdfx_tex.c file.
Yes, you've got it. Thanks.
> Unfortunately, I'm seeing a far worse problem with the tdfx driver now
> with most demos. Triangles are being rendered incorrectly - it's as if
> one of the vertices for each triangle is at screen coordinate (0,0).
> I'm looking into it.
OK, I read your post about the bad RH Glide3 lib, too.
> > But when I enable debug in host.def like below:
> >
> > /* Optionally turn these on for debugging */
> > #define GlxBuiltInTdfx YES
> > /* #define GlxBuiltInI810 YES */
> > /* #define GlxBuiltInMga YES */
> > /* #define GlxBuiltInR128 YES */
> > /* #define GlxBuiltInRadeon YES */
> > #define DoLoadableServer NO
> >
> > Compilation fails with...
> > [-]
> > making all in lib/GL/GL...
> > make[5]: Entering directory `/tmp/INSTALL/SOURCE/dri/xc/xc/lib/GL/GL'
> > make[5]: *** No rule to make target `../../../lib/GL/mesa/dri/?*.o',
> > needed by `libGL.so.1.
> > 2'. Stop.
> > make[5]: Leaving directory `/tmp/INSTALL/SOURCE/dri/xc/xc/lib/GL/GL'
> > make[4]: *** [all] Error 2
> > make[4]: Leaving directory `/tmp/INSTALL/SOURCE/dri/xc/xc/lib/GL'
> > make[3]: *** [all] Error 2
> > make[3]: Leaving directory `/tmp/INSTALL/SOURCE/dri/xc/xc/lib'
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory `/tmp/INSTALL/SOURCE/dri/xc/xc'
> > make[1]: *** [Everything] Error 2
> > make[1]: Leaving directory `/tmp/INSTALL/SOURCE/dri/xc/xc'
> > make: *** [Everything] Error 2
> >
> > What's wrong?
>
> I don't know. Maybe a fresh build would be a good idea.
I always did a complete rebuild?
Do I have to enabled something more/different?
I read through the "new" devel stuff at dri.sourceforge.net, but there is
nothing usefull. Some more info for profiling would be helpfull, too.
Now, only the remaining Glide3 3DNow! texture bug.
I've taken the below stuff from an older post:
[-]
Loaded symbols for /usr/X11R6/lib/modules/dri/tdfx_dri.so
Reading symbols from /usr/lib/libglide3.so...done.
Loaded symbols for /usr/lib/libglide3.so
Reading symbols from /usr/X11R6/lib/libXxf86dga.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXxf86dga.so.1
Reading symbols from /usr/X11R6/lib/libXxf86vm.so.1...done.
Loaded symbols for /usr/X11R6/lib/libXxf86vm.so.1
#0 0x466aaac6 in _trisetup_3DNow_win_nocull_valid ()
from /usr/lib/libglide3.so
(gdb) bt full
#0 0x466aaac6 in _trisetup_3DNow_win_nocull_valid ()
from /usr/lib/libglide3.so
No symbol table info available.
#1 0x00000003 in ?? ()
No symbol table info available.
Error accessing memory address 0x3: No such process.
And last thing is the slowdown from the tdfx-3-5-branch to the tdfx-4-0-branch
(ipers or VTK for example).
Cheers,
Dieter
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
