All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael D. Crawford" <crawford@goingware.com>
To: linux-kernel@vger.kernel.org, newbie@xfree86.org
Subject: Re: DRI doesn't work on 2.4.0 but does on prerelease-ac5
Date: Mon, 08 Jan 2001 18:35:43 +0000	[thread overview]
Message-ID: <3A5A087F.F1C45380@goingware.com> (raw)

OK, I built XFree86 4.0.2 and DRI seems to be working for me now under
2.4.0-ac4.  (Starting with 2.4.0, it wouldn't, this is with an ATI XPert 2000
AGP).

BUT - although /var/log/XFree86.0.log documents the startup of DRI, DRM and AGP,
and states the info about their initialization and stuff so that it looks like
they're working, I don't notice any performance difference running any of the
Mesa-3.4 demos whether or not I use DRI, and whether I run 4.0.1 or 4.0.2.

This makes me suspect it's not really working, or else my build of the Mesa-3.4
library wasn't configured right - but note that if I disable DRI, one of the
Mesa demos will comment that it's not available.

A specific example is Mesa-3.4/demos/gloss.  It's a rotating textured cylinder
that is partially reflective of what seems to be a landscape that is in front of
the screen being reflecting back to the viewer.  I get a pretty consistent 7.5
frames per second:

- in 4.0.1 with no DRI
- in 4.0.1 with DRI
- in 4.0.2 with no DRI
- in 4.0.2 with DRI

Having agpgart and drm/r128 compiled in or as modules also doesn't appear to
make a difference.

The frame rate for gloss drops to about 3.5 if I run geartrain (another demo)
alongside it.  Geartrain by itself seems to be about the same speed in all
cases, though it doesn't report a number.

There are a couple benchmarking tools in Mesa if someone wanted hard numbers
from me.

Can anyone suggest any 3D code that I can download that does more complex things
than the mesa demos that I can test this with?

Is my DRI really working?  If not, any tips on getting it to do so?

Mike
-- 
Michael D. Crawford
GoingWare Inc. - Expert Software Development and Consulting
http://www.goingware.com/
crawford@goingware.com

   Tilting at Windmills for a Better Tomorrow.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-08 22:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-08 18:35 Michael D. Crawford [this message]
2001-01-08 22:06 ` DRI doesn't work on 2.4.0 but does on prerelease-ac5 Bill Nottingham
2001-01-08 22:55 ` khromy
2001-01-08 22:56 ` [OT]: " J Sloan
2001-01-08 23:57   ` Ragnar Hojland Espinosa
2001-01-09  0:37     ` J Sloan
2001-01-09 16:11       ` Ragnar Hojland Espinosa
2001-01-10  7:41         ` xircom_tulip + NFS hanging interface Pau
2001-01-09  8:20   ` [OT]: DRI doesn't work on 2.4.0 but does on prerelease-ac5 Alan Olsen
  -- strict thread matches above, loose matches on Subject: below --
2001-01-10 13:02 Gareth Hughes
2001-01-10  4:21 Bill Crawford
2001-01-10  4:37 ` Alan Cox
2001-01-10  5:18   ` Alan Olsen
2001-01-08 22:45 Michael D. Crawford
2001-01-09 16:17 ` Ragnar Hojland Espinosa
2001-01-06 23:20 Michael D. Crawford
2001-01-07  3:30 ` Alan Olsen
2001-01-07 17:55   ` Dax Kelson
2001-01-07 19:11 ` Jeff Hartmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A5A087F.F1C45380@goingware.com \
    --to=crawford@goingware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=newbie@xfree86.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.