<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - [NV44] dual-link tmds no longer allowed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=40747#c21">Comment # 21</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED --- - [NV44] dual-link tmds no longer allowed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=40747">bug 40747</a>
from <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=40747#c20">comment #20</a>)
<span class="quote">> huh?
> i said that it is *easy* to convince the kernel to pick the right mode. it's
> picking a wrong one only automatically.</span >
Really? It sounds to me like you managed to fool the drm mode-verification
logic (or nouveau's is implemented incorrectly). If it was merely picking the
wrong one, the 1600x1200 one would be in the mode list, and it is not.
<span class="quote">> there is no hardware limitation at all here.</span >
Maybe, maybe not. Should be fairly easy to check. One way to do that would be
to try the thing I said. Or to change the 165mhz check to be >= 0x44 instead of
0x46.
<span class="quote">> X appears more tenacious, apparently because it filters out the good mode
> earlier in the process. it's beyond me why it does that - it makes no sense</span >
It just gets the list from the kernel. What's in
/sys/class/drm/card0-DVI-I-1/modes (or whatever the connector is)? The thing
you (or someone else) saw with X seeing the 1600x1200 mode was it reading it
from DDC. But I'm pretty sure it doesn't care about that -- X doesn't handle
modesetting, the kernel does, and it uses its mode list.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>