Re: [Dri-users] DRI, GL support, and an ATI Rage Mobility chipset...

[<the...@ya...>]

 --- magenta <ma...@tr...> wrote: > On Sat, Dec 28, 2002 at
06:25:08PM +0000, Stween wrote:
> > > > I also find that the performance isn't over-impressive. 
> glxgears
> > > runs
> > > > at almost exactly the same speed with DRI as without (~200fps).
> 
> > > Have
> > > > you tried turning the screen resolution and/or colour depth
> down to
> > > > speed things up?
> > > 
> > > Changing resolution shouldn't affect things with direct
> rendering.
> > > glxgears is  certainly not fillrae-bound; if anything it's
> > > state-change-bound.
> > 
> > Well, glxgears running fullscreen at 1024*768 comes in at around
> 27fps.
> > I can turn the resolution down in glquake, and at 640*480 it runs
> at a
> > half-decent speed (as long as I don't pull down that transparent
> > console), but what's the point if software rendered x11quake runs
> > faster at the same resolution??
> 
> It sounds like you're not actually getting direct rendering then. 
> Check
> glxinfo to make sure that direct rendering is actually enabled.  Also
> try
> enabling libGL debugging (export LIBGL_DEBUG=verbose in [ba]sh,
> setenv
> LIBGL_DEBUG verbose in [t]csh).

Ok, I set LIBGL_DEBUG, and what I see when I run glquake is:

"libGL: XF86DRIGetClientDriverName: 6.4.8 mach64 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/mach64_dri.so
libGL: OpenDriver: trying /usr/X11R6/lib/modules/dri/mach64_dri.so
drmOpenByBusid: busid is PCI:1:0:0
drmOpenDevice: minor is 0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 7, (OK)
drmOpenByBusid: drmOpenMinor returns 7
drmOpenByBusid: drmGetBusid reports PCI:1:0:0"

I don't know what much of it means, but I don't see any errors, and
glxinfo does indeed say "direct rendering: Yes"...

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com