[Bug 75345] [HD4600 regression] DVI does not support dual-link
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Mar 26 06:40:55 PDT 2014
https://bugs.freedesktop.org/show_bug.cgi?id=75345
Chris Wilson <chris at chris-wilson.co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to comment #8)
> I should add the DVI output is reported by KMS as a HDMI output, so perhaps
> it's not possible to identify it as a DVI port and limit the bandwidth? If
> this is correct, then in theory one should be able to connect a HDMI 1.4
> capable monitor (not mine) to the DVI port with a passive adapter, and get
> 2560x1600 at 60Hz.
In theory, yes. You are still going beyond the cable spec so there is some
danger that you would lose the signal.
If we ignore the ongoing issue with HDMI->active dual-DVI links, this here bug
is fixed by
commit 6375b768a9850b6154478993e5fb566fa4614a9c
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date: Mon Mar 3 11:33:36 2014 +0200
drm/i915: Reject >165MHz modes w/ DVI monitors
Single-link DVI max dotclock is 165MHz. Filter out modes with higher
dotclock when the monitor doesn't support HDMI.
Modes higher than 165 MHz were allowed in
commit 7d148ef51a657fd04036c3ed7803da600dd0d451
Author: Daniel Vetter <daniel.vetter at ffwll.ch>
Date: Mon Jul 22 18:02:39 2013 +0200
drm/i915: fix hdmi portclock limits
Also don't attempt to use 12bpc mode with DVI monitors.
Cc: Adam Nielsen <a.nielsen at shikadi.net>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75345
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=70331
Tested-by: Ralf Jung <post+kernel at ralfj.de>
Cc: stable at vger.kernel.org
Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
Signed-off-by: Jani Nikula <jani.nikula at intel.com>
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140326/30c03aaf/attachment.html>
More information about the intel-gfx-bugs
mailing list