From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75992] Display freezes & corruption with an r7 260x on 3.14-rc6
Date: Fri, 11 Apr 2014 11:58:25 +0000 [thread overview]
Message-ID: <bug-75992-502-8x8KKPILDZ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75992-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1037 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=75992
--- Comment #45 from Ed Tomlinson <edt@aei.ca> ---
Good news.
I rebuilt linux-git with the newer mc ucode patch and manually replaced the
BONAIRE_mc.bin firmware file and rebuilt my initrd.
uniengine tropical completes at 33fps (fullscreen 1920x1200)
uniengine sanctuary completes at 45fps (fullscreen 1920x1200)
tropical is the test that usually killed things quickly. It ran at about 30fps
when it worked at all on .14 and about 40fps on .15 with old firmware. fglrx
manages about 80fps.
That being said the new firmware is not as fluid as the older. There are times
that there are hesitations when the camera is panning which I did not notice
previously. However my tests do run without stalling or corruption.
Would you like me to test with and without the patch on .14?
You can add my tested-by to the 'newer mc ucode patch' for linux-git
'Tested-by: Ed Tomlinson <edtoml@gmail.com>'
THANKS!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1876 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
next prev parent reply other threads:[~2014-04-11 11:58 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 17:25 [Bug 75992] New: Display freezes & corruption with an r7 260x on 3.14-rc6 bugzilla-daemon
2014-03-10 17:25 ` [Bug 75992] " bugzilla-daemon
2014-03-10 17:28 ` bugzilla-daemon
2014-03-10 20:33 ` bugzilla-daemon
2014-03-23 20:04 ` bugzilla-daemon
2014-03-24 14:55 ` bugzilla-daemon
2014-03-25 13:00 ` bugzilla-daemon
2014-03-25 14:55 ` bugzilla-daemon
2014-03-26 17:33 ` bugzilla-daemon
2014-03-27 14:36 ` bugzilla-daemon
2014-03-27 18:53 ` bugzilla-daemon
2014-03-27 22:08 ` bugzilla-daemon
2014-03-28 12:13 ` bugzilla-daemon
2014-03-28 12:19 ` bugzilla-daemon
2014-03-28 14:12 ` bugzilla-daemon
2014-03-28 17:28 ` bugzilla-daemon
2014-03-28 18:18 ` bugzilla-daemon
2014-03-28 20:09 ` bugzilla-daemon
2014-03-28 23:07 ` bugzilla-daemon
2014-04-02 16:49 ` bugzilla-daemon
2014-04-02 22:31 ` bugzilla-daemon
2014-04-07 17:18 ` bugzilla-daemon
2014-04-10 15:19 ` bugzilla-daemon
2014-04-10 17:30 ` bugzilla-daemon
2014-04-10 17:35 ` bugzilla-daemon
2014-04-10 18:37 ` bugzilla-daemon
2014-04-10 18:44 ` bugzilla-daemon
2014-04-10 19:05 ` bugzilla-daemon
2014-04-10 19:10 ` bugzilla-daemon
2014-04-10 20:26 ` bugzilla-daemon
2014-04-10 20:36 ` bugzilla-daemon
2014-04-10 21:03 ` bugzilla-daemon
2014-04-10 21:30 ` bugzilla-daemon
2014-04-10 21:45 ` bugzilla-daemon
2014-04-10 21:47 ` bugzilla-daemon
2014-04-10 21:50 ` bugzilla-daemon
2014-04-10 22:09 ` bugzilla-daemon
2014-04-10 23:40 ` bugzilla-daemon
2014-04-11 0:59 ` bugzilla-daemon
2014-04-11 3:02 ` bugzilla-daemon
2014-04-11 3:11 ` bugzilla-daemon
2014-04-11 7:45 ` bugzilla-daemon
2014-04-11 8:57 ` bugzilla-daemon
2014-04-11 9:25 ` bugzilla-daemon
2014-04-11 11:17 ` bugzilla-daemon
2014-04-11 11:18 ` bugzilla-daemon
2014-04-11 11:58 ` bugzilla-daemon [this message]
2014-04-11 12:15 ` bugzilla-daemon
2014-04-11 22:10 ` bugzilla-daemon
2014-04-11 22:17 ` bugzilla-daemon
2014-04-11 22:32 ` bugzilla-daemon
2014-04-13 5:07 ` bugzilla-daemon
2014-04-13 13:03 ` bugzilla-daemon
2014-04-14 0:32 ` bugzilla-daemon
2014-05-08 16:23 ` bugzilla-daemon
2014-05-08 16:25 ` bugzilla-daemon
2014-05-14 11:30 ` bugzilla-daemon
2014-05-14 11:52 ` bugzilla-daemon
2014-05-14 21:36 ` bugzilla-daemon
2014-05-14 21:39 ` bugzilla-daemon
2014-05-14 21:45 ` bugzilla-daemon
2019-11-20 7:58 ` 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-75992-502-8x8KKPILDZ@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