Re: [Dri-devel] Problems: Voodoo 5 detected as "Voodoo4", 3D games freezing

[Brian P. <br...@va...>]

Oliver Feiler wrote:
> 
> Brian Paul wrote:
> > >
> > >         I am not sure if this is correct, since both programs report a
> > > "Voodoo4", while my friend has a Voodoo 5 card. I was able to trace
> > > this back to the Glide library (CVS snapshot 22-12-2000), which seems
> > > to detect only one chip on the card, even though it looks like there
> > > is support for up to four chips in the library.
> >
> > When Glide is updated for Voodoo5's second chip, the glGetString(GL_RENDERER)
> > call will report Voodoo5 instead of Voodoo4.
> 
>         Hmm, I thought with the tdfx-3-0-0 merge supports both chips now. I
> thought I remember someone saying (I think it was on the dri-users list some
> time ago) that he got about 1400 fps with gears -info which is pretty much
> twice what I get.

That might have been a preliminary result from Daryll.  The dual-chip,
SLI code is not finished.


>         I have another question about glide3 compiling with 3DNow!. When I
> compile glide with 3DNow! support DRI will be disabled because of an
> undefinded symbol (_trisetup_Default_win_nocull_invalid) in the glide library.
> Compiling glide without 3DNow! results in a library with
> 
> 00031dc0 T _trisetup_Default_clip_nocull_invalid
> 00031dc0 T _trisetup_Default_clip_nocull_valid
> 00031dc0 T _trisetup_Default_win_nocull_invalid
> 00032120 T _trisetup_Default_win_nocull_valid
> 
>         Compiling with 3DNow! resulsts in
> 
> 00031f80 T _trisetup_3DNow_clip_nocull_invalid
> 00031f80 T _trisetup_3DNow_clip_nocull_valid
> 00031f80 T _trisetup_3DNow_win_nocull_invalid
> 00032740 T _trisetup_3DNow_win_nocull_valid
>          U _trisetup_Default_win_nocull_invalid
>          U _trisetup_Default_win_nocull_valid
> 
>         With the _Default_ symbol undefined DRI gets disabled.

Others have also reported problems with Glide and 3DNow!  You'll
probably have to disable the 3DNow! optimizations.

-Brian