From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes
Date: Thu, 01 Mar 2018 19:41:14 +0000 [thread overview]
Message-ID: <bug-105302-502-bGQZTOaZr9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105302-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 711 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105302
--- Comment #2 from Harry Wentland <harry.wentland@amd.com> ---
I don't have the spec right now but wikipedia has a nice run-down of the DVI
bounding box: https://en.wikipedia.org/wiki/Digital_Visual_Interface#Digital
Basically 2560x1600 @ 60Hz is the highest allowed for dual-link, which is just
a tad above your 2560x1440 @ 60Hz. 110Hz at full resolution would definitely
not be supported by DVI.
What monitor are you using? Is it intended to support 110Hz at full resolution
on DVI? Could it be that this full monitor capabilities are only supported
through DP?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1618 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-01 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 5:34 [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes bugzilla-daemon
2018-03-01 14:49 ` bugzilla-daemon
2018-03-01 19:41 ` bugzilla-daemon [this message]
2018-03-01 23:42 ` bugzilla-daemon
2018-03-02 15:03 ` bugzilla-daemon
2018-03-02 15:39 ` bugzilla-daemon
2018-03-08 9:06 ` bugzilla-daemon
2019-11-19 8:31 ` 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-105302-502-bGQZTOaZr9@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