All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49981] On HD6850, Power Profile doesn't change if 2 screen is attached.
Date: Tue, 02 Oct 2012 13:14:21 +0000	[thread overview]
Message-ID: <bug-49981-502-PCkAUjAEBv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49981-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 764 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=49981

--- Comment #15 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #14)
> I don't think that is correct. It can clearly be seen in Windows that Barts
> uses different idles for multi head than it does for single head, but uses
> the same mid and high. Cayman has a different system to barts too I suspect.

Windows has a very different implementation at the moment, but uses the tables
in a similar manor.

> Isn't that dangerous? It makes the card operate outside of the bios table
> profiles. You would, in some cases, be increasing the memory clock without
> increasing the voltage.

Good catch.  Fixed in v3 of the patch.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1678 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

  parent reply	other threads:[~2012-10-02 13:14 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-49981-502@http.bugs.freedesktop.org/>
2012-05-16  0:27 ` [Bug 49981] On HD6850, Power Profile doesn't change if 2 screen is attached bugzilla-daemon
2012-05-31  2:13 ` bugzilla-daemon
2012-05-31  2:15 ` bugzilla-daemon
2012-09-28 14:32 ` bugzilla-daemon
2012-09-29 17:23 ` bugzilla-daemon
2012-09-30 15:57 ` bugzilla-daemon
2012-09-30 15:58 ` bugzilla-daemon
2012-09-30 16:52 ` bugzilla-daemon
2012-09-30 17:09 ` bugzilla-daemon
2012-09-30 23:16 ` bugzilla-daemon
2012-10-01  1:40 ` bugzilla-daemon
2012-10-01 17:43 ` bugzilla-daemon
2012-10-01 21:44 ` bugzilla-daemon
2012-10-01 23:28 ` bugzilla-daemon
2012-10-02  9:40 ` bugzilla-daemon
2012-10-02 13:14 ` bugzilla-daemon [this message]
2012-10-02 13:34 ` bugzilla-daemon
2012-10-02 13:44 ` bugzilla-daemon
2012-10-02 13:49 ` bugzilla-daemon
2012-10-02 14:07 ` bugzilla-daemon
2012-10-02 14:18 ` bugzilla-daemon
2012-10-02 14:35 ` bugzilla-daemon
2012-10-02 14:42 ` bugzilla-daemon
2012-10-15 20:56 ` bugzilla-daemon
2012-12-28 16:23 ` bugzilla-daemon
2013-01-01  2:34 ` bugzilla-daemon
2013-02-10 16:48 ` bugzilla-daemon
2013-02-10 17:08 ` bugzilla-daemon
2013-02-11 13:49 ` bugzilla-daemon
2013-02-12 11:36 ` bugzilla-daemon
2013-02-19  2:42 ` bugzilla-daemon
2013-02-20 11:20 ` bugzilla-daemon
2013-04-06  0:51 ` bugzilla-daemon
2013-04-18  0:07 ` bugzilla-daemon
2013-05-23 13:46 ` bugzilla-daemon
2013-08-23 17:37 ` bugzilla-daemon
2013-08-23 17:40 ` bugzilla-daemon
2019-11-19  8:27 ` 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-49981-502-PCkAUjAEBv@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 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.