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 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL
Date: Wed, 26 Oct 2016 15:45:23 +0000	[thread overview]
Message-ID: <bug-98333-502-MoFfcSS49E@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98333-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Harry Wentland <harry.wentland@amd.com> ---
I don't have the same monitor but I don't have any problem lighting up with
HDMI 2.0 4k 60Hz with Alex's amd-staging-4.7 and the commit from a week ago:

commit 4fa58023f62a95e93f82a25cdceb87b19b69b27f
Author: Christian König <christian.koenig@amd.com>
Date:   Mon Oct 17 15:34:07 2016 +0200

    reservation: revert "wait only with non-zero timeout specified (v3)"

    This reverts commit fb8b7d2b9d80e1e71f379e57355936bd2b024be9.

    Otherwise signaling might never be activated on the fences. This can
    result in infinite waiting with hardware which has unreliable interrupts.

    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Chunming Zhou <david1.zhou@amd.com>

If you still see this issue please attach xorg log, dmesg and xrandr output, as
Alex suggested.

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

[-- Attachment #1.2: Type: text/html, Size: 1999 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:[~2016-10-26 15:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 21:04 [Bug 98333] 4K @ 60Hz over HDMI 2.0 not working with AMDGPU-DAL bugzilla-daemon
2016-10-20  3:44 ` bugzilla-daemon
2016-10-26 15:45 ` bugzilla-daemon [this message]
2016-11-03  2:54 ` bugzilla-daemon
2016-11-03  2:59 ` bugzilla-daemon
2016-11-03  4:46 ` bugzilla-daemon
2016-12-02 21:59 ` bugzilla-daemon
2016-12-02 22:02 ` bugzilla-daemon
2017-01-04 11:27 ` bugzilla-daemon
2017-01-04 11:30 ` bugzilla-daemon
2017-01-04 11:31 ` bugzilla-daemon
2017-01-04 11:32 ` bugzilla-daemon
2017-01-04 11:48 ` bugzilla-daemon
2017-01-04 11:49 ` bugzilla-daemon
2017-01-04 11:49 ` bugzilla-daemon
2017-01-05  1:34 ` bugzilla-daemon
2017-02-23  3:10 ` bugzilla-daemon
2017-02-23  3:11 ` bugzilla-daemon
2017-02-23  3:22 ` bugzilla-daemon
2019-11-19  8:11 ` 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-98333-502-MoFfcSS49E@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).