From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94061] [radeon - Kaveri] dpm works badly - much to high power consumption compared to catalyst
Date: Mon, 09 Mar 2015 15:14:40 +0000 [thread overview]
Message-ID: <bug-94061-2300-6XNNI40op3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94061-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94061
--- Comment #6 from Klaus Maier <abcdmail@freenet.de> ---
radeon.bapm=1 brings back the originally reported behaviour (based on 3.14).
I didn't enable rdev->cg_flags and rdev->pg_flags as it is already known to be
broken because it needs a complete kernel recompile.
The relevant code already was in 3.12, which was released 2013-11-03.
When will there be a fix? It is working w/ Catalyst. Why not w/ radeon? Both
drivers are made by AMD finally ... .
--
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
next prev parent reply other threads:[~2015-03-09 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 12:26 [Bug 94061] New: [radeon - Kaveri] dpm works badly - much to high power consumption compared to catalyst bugzilla-daemon
2015-03-02 7:01 ` [Bug 94061] " bugzilla-daemon
2015-03-02 15:50 ` bugzilla-daemon
2015-03-09 11:39 ` bugzilla-daemon
2015-03-09 11:41 ` bugzilla-daemon
2015-03-09 13:39 ` bugzilla-daemon
2015-03-09 15:14 ` bugzilla-daemon [this message]
2015-04-04 9:17 ` bugzilla-daemon
2015-04-04 17:28 ` bugzilla-daemon
2015-04-04 20:49 ` bugzilla-daemon
2020-12-03 17:49 ` bugzilla-daemon
2020-12-03 18:02 ` bugzilla-daemon
2020-12-03 20:02 ` 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-94061-2300-6XNNI40op3@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.