From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207183] radeon.dpm=1 with second monitor runs hot
Date: Fri, 10 Apr 2020 14:15:16 +0000 [thread overview]
Message-ID: <bug-207183-2300-YxzMTJM1xG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207183-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207183
--- Comment #5 from Erik Huelsmann (ehuels@gmail.com) ---
Is the fact that it's apparently not possible to switch the memory clock with 2
monitors attached a design error in the hardware? Unfortunately, I don't have
the Windows setup anymore to investigate it.
I'm extremely happy with my 'radeon.dpm=0' setup, because I'm only doing
text-editing, programming and web browsing.
As I understand it, it's a choice where you have to run a high clock
continually or cause possible on-screen glitches? That's too bad. I personally
wouldn't mind a small flicker if that would help the noise of my laptop, but I
do understand others may make other choices here.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-10 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-09 21:14 [Bug 207183] New: radeon.dpm=1 with second monitor runs hot bugzilla-daemon
2020-04-10 11:45 ` [Bug 207183] " bugzilla-daemon
2020-04-10 12:07 ` bugzilla-daemon
2020-04-10 12:25 ` bugzilla-daemon
2020-04-10 12:38 ` bugzilla-daemon
2020-04-10 14:15 ` bugzilla-daemon [this message]
2020-04-12 15:21 ` 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-207183-2300-YxzMTJM1xG@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 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).