dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.
Date: Thu, 13 Jul 2017 03:28:17 +0000	[thread overview]
Message-ID: <bug-96868-502-3Gdz7gOBCd@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96868-502@http.bugs.freedesktop.org/>


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

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

almoped@gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |---
             Status|RESOLVED                    |REOPENED

--- Comment #31 from almoped@gmail.com ---
Reopened since refresh rates under 120Hz also causes full speed mclk and could
be a logic typo somewhere. Also since 143.9Hz works with lowest mclk, forcing
highest  mclk for rates above 120 might be shooting birds with cannons.

And since 144Hz actually still does not work, but 143.9Hz does. Maybe KDE
causes this minor issue.

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

[-- Attachment #1.2: Type: text/html, Size: 2417 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-07-13  3:28 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-96868-502@http.bugs.freedesktop.org/>
2016-07-11  7:24 ` [Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx bugzilla-daemon
2016-07-11  9:31 ` bugzilla-daemon
2016-07-11  9:32 ` bugzilla-daemon
2016-07-11  9:50 ` bugzilla-daemon
2016-07-11  9:50 ` bugzilla-daemon
2016-07-11 14:56 ` bugzilla-daemon
2016-07-11 14:57 ` bugzilla-daemon
2016-07-11 19:26 ` bugzilla-daemon
2016-07-11 19:28 ` bugzilla-daemon
2016-07-12 22:36 ` bugzilla-daemon
2016-10-05  8:33 ` bugzilla-daemon
2016-11-26 19:38 ` bugzilla-daemon
2016-11-26 21:02 ` bugzilla-daemon
2016-11-29 15:41 ` bugzilla-daemon
2017-03-18 18:31 ` bugzilla-daemon
2017-05-11  9:48 ` bugzilla-daemon
2017-05-11 13:01 ` bugzilla-daemon
2017-05-11 15:04 ` bugzilla-daemon
2017-05-11 16:41 ` bugzilla-daemon
2017-05-11 17:59 ` bugzilla-daemon
2017-05-11 18:00 ` bugzilla-daemon
2017-05-11 18:00 ` bugzilla-daemon
2017-05-11 18:00 ` bugzilla-daemon
2017-05-12  9:22 ` bugzilla-daemon
2017-05-23 21:24 ` bugzilla-daemon
2017-05-23 21:24 ` bugzilla-daemon
2017-05-23 21:25 ` bugzilla-daemon
2017-05-23 21:25 ` bugzilla-daemon
2017-05-23 21:26 ` bugzilla-daemon
2017-05-24 15:13 ` bugzilla-daemon
2017-06-14 13:28 ` bugzilla-daemon
2017-06-14 13:51 ` bugzilla-daemon
2017-07-13  3:08 ` bugzilla-daemon
2017-07-13  3:28 ` bugzilla-daemon [this message]
2017-10-04 23:22 ` bugzilla-daemon
2018-02-09 22:37 ` bugzilla-daemon
2018-03-24 11:51 ` bugzilla-daemon
2018-11-10 18:48 ` bugzilla-daemon
2018-11-10 18:51 ` bugzilla-daemon
2018-11-29 20:51 ` bugzilla-daemon
2018-11-30  1:26 ` 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-96868-502-3Gdz7gOBCd@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).