From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104660] DC R9 285 dual link DVI modes not shown.
Date: Tue, 16 Jan 2018 19:27:47 +0000 [thread overview]
Message-ID: <bug-104660-502-PfJ5KWjI7x@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104660-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 993 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104660
--- Comment #3 from Andy Furniss <adf.lists@gmail.com> ---
Thanks, that works.
This is the same with non dc, but is there a reason they are a bit low?
1920x1080 (0x5b) 285.500MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 137.26KHz
v: height 1080 start 1083 end 1088 total 1144 clock 119.98Hz
1920x1080 (0x5c) 260.250MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 125.12KHz
v: height 1080 start 1083 end 1088 total 1138 clock 109.95Hz
1920x1080 (0x5d) 235.500MHz +HSync -VSync
h: width 1920 start 1968 end 2000 total 2080 skew 0 clock 113.22KHz
v: height 1080 start 1083 end 1088 total 1133 clock 99.93Hz
I was hoping DC would differ from the old driver in giving exact Hz for these.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1758 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-01-16 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 18:18 [Bug 104660] DC R9 285 dual link DVI modes not shown bugzilla-daemon
2018-01-16 18:19 ` bugzilla-daemon
2018-01-16 18:54 ` bugzilla-daemon
2018-01-16 19:27 ` bugzilla-daemon [this message]
2018-01-16 19:31 ` bugzilla-daemon
2018-01-16 19:38 ` bugzilla-daemon
2018-01-29 23:46 ` 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-104660-502-PfJ5KWjI7x@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