All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 86891] AMD/ATI Tahiti XT 7970 - long lags/stutters in games
Date: Wed, 29 Oct 2014 19:34:21 +0000	[thread overview]
Message-ID: <bug-86891-2300-SCWX5zroSw@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86891-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=86891

--- Comment #10 from Michael Mair-Keimberger <bu9zilla@gmail.com> ---
(In reply to Michel Dänzer from comment #7)
> Does Mesa 10.3.2 work better, specifically commit
> 64c2bdc334ba472603b1e7cd2c3046cfbce285b6?

I'll get slightly better results with 10.3.2 (with 3.18rc1):
FPS: 16.6
Score: 694
Min FPS: 3.7
Max FPS: 33.1

But honestly, watching the demo feels like it got even worse. Still very long
lag's, especially at the beginning of new scene's (before it starts to render).

(In reply to Dieter Nützel from comment #8)
> Alex's drm-next-3.19-wip (it shows 3.17-rc5 ;-) for example:
> git clone git://people.freedesktop.org/~agd5f/linux/ drm-next-3.19-wip
> 
> If you have it already, get it or change it to another tree:
> cd drm-next-3.19-wip
> git checkout -b drm-next-3.19-wip remotes/origin/drm-next-3.19-wip
> 
> Sometimes you need this:
> git fetch origin
> git reset --hard origin/drm-next-3.19-wip

I've just started cloning drm-next-3.19 but freedesktop seems to be quite slow
- looks like i can start testing it tomorrow :/

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-10-29 19:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 15:28 [Bug 86891] New: AMD/ATI Tahiti XT 7970 - long lags/stutters in games bugzilla-daemon
2014-10-26 18:48 ` [Bug 86891] " bugzilla-daemon
2014-10-27 18:26 ` bugzilla-daemon
2014-10-27 20:25 ` bugzilla-daemon
2014-10-27 20:30 ` bugzilla-daemon
2014-10-27 22:45 ` bugzilla-daemon
2014-10-28  8:04 ` bugzilla-daemon
2014-10-29  8:46 ` bugzilla-daemon
2014-10-29 17:10 ` bugzilla-daemon
2014-10-29 17:26 ` bugzilla-daemon
2014-10-29 19:34 ` bugzilla-daemon [this message]
2014-10-29 22:04 ` bugzilla-daemon
2014-10-29 22:06 ` bugzilla-daemon
2014-10-30  3:17 ` bugzilla-daemon
2014-10-30 19:33 ` bugzilla-daemon
2014-10-30 22:29 ` bugzilla-daemon
2014-10-30 22:30 ` bugzilla-daemon
2014-10-31  3:28 ` bugzilla-daemon
2014-11-01 17:27 ` bugzilla-daemon
2014-11-01 19:45 ` bugzilla-daemon
2014-11-02 10:33 ` bugzilla-daemon
2014-11-02 10:41 ` bugzilla-daemon
2014-12-10 17:55 ` 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-86891-2300-SCWX5zroSw@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 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.