From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100919] "Out of range" on a display connected to a DVI-D output of RX460 card via DVI-D<=>HDMI-A cable
Date: Wed, 03 May 2017 19:12:30 +0000 [thread overview]
Message-ID: <bug-100919-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100919
Bug ID: 100919
Summary: "Out of range" on a display connected to a DVI-D
output of RX460 card via DVI-D<=>HDMI-A cable
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: nikola.forro@gmail.com
I'm using the latest code from amd-staging-4.9 branch of ~agd5f/linux.
The problem is caused by this commit:
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=amd-staging-4.9&id=2b2d4cfb0a629961a44e1ea0b29d336c1336deb9
After this change, when sink_signal is DVI_DUAL_LINK but pix_clk_khz is lower
than TMDS_MAX_PIXEL_CLOCK_IN_KHZ, stream->signal is set to DVI_DUAL_LINK, while
previously it was being set to DVI_SINGLE_LINK.
As a result, the connected display just reports "Out of range" error.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2643 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 reply other threads:[~2017-05-03 19:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 19:12 bugzilla-daemon [this message]
2017-05-08 8:20 ` [Bug 100919] [DC] "Out of range" on a display connected to a DVI-D output of RX460 card via DVI-D<=>HDMI-A cable bugzilla-daemon
2017-05-09 4:01 ` bugzilla-daemon
2017-05-09 4:02 ` bugzilla-daemon
2017-05-09 14:54 ` bugzilla-daemon
2017-05-09 17:12 ` bugzilla-daemon
2017-05-09 17:24 ` bugzilla-daemon
2017-05-09 17:29 ` bugzilla-daemon
2017-05-09 17:34 ` bugzilla-daemon
2017-05-09 17:40 ` bugzilla-daemon
2017-05-09 18:13 ` bugzilla-daemon
2017-05-26 14:32 ` bugzilla-daemon
2017-05-26 14:33 ` bugzilla-daemon
2017-05-26 15:21 ` bugzilla-daemon
2018-02-19 7:31 ` bugzilla-daemon
2018-02-20 19:38 ` bugzilla-daemon
2018-02-26 15:43 ` bugzilla-daemon
2018-02-26 15:50 ` bugzilla-daemon
2018-03-09 14:02 ` 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-100919-502@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.