From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes Date: Thu, 01 Mar 2018 23:42:49 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1146565060==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 36F896EDCE for ; Thu, 1 Mar 2018 23:42:49 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1146565060== Content-Type: multipart/alternative; boundary="15199477690.98CcCB1.31462" Content-Transfer-Encoding: 7bit --15199477690.98CcCB1.31462 Date: Thu, 1 Mar 2018 23:42:49 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105302 --- Comment #3 from Andrew Sheldon --- (In reply to Harry Wentland from comment #2) > 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#Digi= tal >=20 > 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. >=20 > 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 on= ly > supported through DP? It's a cheap Korean monitor that only supports DVI-D (Qnix qx2710 single in= put version), and unofficially supports greater than 60hz. You're right, it's a= bove DVI-D spec but it would be nice to have an option to use higher pixel clocks nevertheless. The Nvidia binary drivers have the option for ignoring the pi= xel clock check so there is at least one example of this being supported in the wild. --=20 You are receiving this mail because: You are the assignee for the bug.= --15199477690.98CcCB1.31462 Date: Thu, 1 Mar 2018 23:42:49 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 3 on bug 10530= 2 from Andrew Sheldon 
(In reply to Harry Wentland from comment #2)
> I don't have the spec right now but wikipedia ha=
s a nice run-down of the DVI
> bounding box: https://en.wikipedia.org/wiki/Digital_Visual_Interface#D=
igital
>=20
> Basically 2560x1600 @ 60Hz is the highest allowed for dual-link, w=
hich is
> just a tad above your 2560x1440 @ 60Hz. 110Hz at full resolution w=
ould
> definitely not be supported by DVI.
>=20
> 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?

It's a cheap Korean monitor that only supports DVI-D (Qnix qx2710 single in=
put
version), and unofficially supports greater than 60hz. You're right, it's a=
bove
DVI-D spec but it would be nice to have an option to use higher pixel clocks
nevertheless. The Nvidia binary drivers have the option for ignoring the pi=
xel
clock check so there is at least one example of this being supported in the
wild.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15199477690.98CcCB1.31462-- --===============1146565060== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1146565060==--