From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board
Date: Fri, 26 Sep 2014 22:10:59 +0000 [thread overview]
Message-ID: <bug-69721-502-pBnBmNLXx5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69721-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 587 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69721
Alexandre Demers <alexandre.f.demers@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
Closing since it should be fixed in kernel 3.18 (pull request from
drm-next-3.18).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2272 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
prev parent reply other threads:[~2014-09-26 22:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 16:13 [Bug 69721] New: Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g bugzilla-daemon
2013-09-23 16:14 ` [Bug 69721] " bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
2013-09-23 23:03 ` [Bug 69721] Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board bugzilla-daemon
2014-09-22 4:30 ` bugzilla-daemon
2014-09-22 14:18 ` bugzilla-daemon
2014-09-22 16:19 ` bugzilla-daemon
2014-09-22 16:31 ` bugzilla-daemon
2014-09-22 19:30 ` bugzilla-daemon
2014-09-23 4:43 ` bugzilla-daemon
2014-09-26 22:10 ` bugzilla-daemon [this message]
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-69721-502-pBnBmNLXx5@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).