dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69497] New: X1950XTX performance issue
Date: Tue, 17 Sep 2013 21:42:16 +0000	[thread overview]
Message-ID: <bug-69497-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=69497

          Priority: medium
            Bug ID: 69497
          Assignee: dri-devel@lists.freedesktop.org
           Summary: X1950XTX performance issue
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: darkbasic@linuxsystems.it
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

I don't care much because I don't use this card anymore, but since I did some
benchmarks I will report it because I know there are still a lot of peoples who
use R300g.

http://openbenchmarking.org/result/1309172-SO-X1950XTX238

I got 37 fps in openarena with the X1950XTX, while it should be at least 70+
(http://www.phoronix.com/scan.php?page=article&item=amd_r300g_mesa92&num=2)

Kernel 3.12
System logs: http://openbenchmarking.org/system/1309172-SO-X1950XTX238/x1950xtx

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2559 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-09-17 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 21:42 bugzilla-daemon [this message]
2019-11-19  8:38 ` [Bug 69497] X1950XTX performance issue bugzilla-daemon

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=bug-69497-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).