From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91861] [Radeon RS780] Blank screen (no signal) on HDMI after boot in 3.15 & later
Date: Sun, 01 Feb 2015 22:19:02 +0000 [thread overview]
Message-ID: <bug-91861-2300-CMlLfPRoPc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-91861-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=91861
--- Comment #13 from Mike S. <michael.selig@fs.com.au> ---
Wow, thank you very much for the detailed explanation :-)
Though all I was really expecting was a "yes/no or not sure" answer to whether
the new higher values of fb_dev & ref_div on my RS780 could be responsible for
pushing the PLL "closer to the edge" than with the driver on kernel 3.14, and
therefore maybe less stable and/or produce more heat.
So, from your explanation, using a ref_div of 7 compared to 2, means that the
VCO is running at a higher frequency, and hence, higher voltage. So I assume
that would mean the GPU would be drawing more power & therefore run hotter,
though I am not sure how significant this is to its overall power use.
Is that right?
The reason I would like to know this is to determine whether the new divider
numbers would cause the GPU to be less stable & hotter, which is fairly
important in a HTPC where I am trying to keep fan noise to a minimum. If so, I
might then try to force the ref_div below 7 in the driver (as I know it has
been stable for several years at 2).
--
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-02-01 22:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 7:29 [Bug 91861] New: [Radeon RS780] Blank screen (no signal) on HDMI after boot in 3.15 & later bugzilla-daemon
2015-01-23 7:35 ` [Bug 91861] " bugzilla-daemon
2015-01-23 19:15 ` bugzilla-daemon
2015-01-24 11:05 ` bugzilla-daemon
2015-01-27 8:08 ` bugzilla-daemon
2015-01-27 9:15 ` bugzilla-daemon
2015-01-28 23:46 ` bugzilla-daemon
2015-01-29 13:00 ` bugzilla-daemon
2015-01-29 22:20 ` bugzilla-daemon
2015-01-30 1:21 ` bugzilla-daemon
2015-01-30 15:43 ` bugzilla-daemon
2015-01-30 22:44 ` bugzilla-daemon
2015-01-31 9:55 ` bugzilla-daemon
2015-02-01 22:19 ` bugzilla-daemon [this message]
2015-02-06 9:44 ` bugzilla-daemon
2015-02-06 9:52 ` bugzilla-daemon
2015-02-06 10:08 ` bugzilla-daemon
2015-02-06 10:20 ` 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-91861-2300-CMlLfPRoPc@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.