From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104412] RX 460 HDMI 4k 60fps not working, DisplayPort is.
Date: Tue, 27 Mar 2018 18:48:29 +0000 [thread overview]
Message-ID: <bug-104412-502-R8FnFbwp7D@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104412-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 365 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #13 from Harry Wentland <harry.wentland@amd.com> ---
The problem with 4k60 being blocked due to a BIOS bit should be fixed now. I
recommend trying the drm-next-4.17-wip from
https://cgit.freedesktop.org/~agd5f/linux
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1210 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
next prev parent reply other threads:[~2018-03-27 18:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 13:33 [Bug 104412] RX 460 HDMI 4k 60fps not working, DisplayPort is bugzilla-daemon
2017-12-29 13:33 ` bugzilla-daemon
2017-12-29 13:34 ` bugzilla-daemon
2017-12-29 15:47 ` bugzilla-daemon
2017-12-29 20:08 ` bugzilla-daemon
2017-12-29 20:15 ` bugzilla-daemon
2017-12-30 12:10 ` bugzilla-daemon
2017-12-30 12:40 ` bugzilla-daemon
2018-01-18 21:51 ` bugzilla-daemon
2018-01-18 21:56 ` bugzilla-daemon
2018-01-19 16:06 ` bugzilla-daemon
2018-01-20 1:41 ` bugzilla-daemon
2018-03-27 2:12 ` bugzilla-daemon
2018-03-27 18:48 ` bugzilla-daemon [this message]
2018-03-27 19:04 ` bugzilla-daemon
2018-04-05 17:40 ` bugzilla-daemon
2018-04-05 21:43 ` bugzilla-daemon
2018-04-15 13:57 ` bugzilla-daemon
2018-04-17 18:13 ` bugzilla-daemon
2018-04-25 15:32 ` 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-104412-502-R8FnFbwp7D@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