<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - i195: modesetting stops working on kernel 4.17, works fine on 4.16"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106804#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - i195: modesetting stops working on kernel 4.17, works fine on 4.16"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106804">bug 106804</a>
from <span class="vcard"><a class="email" href="mailto:ville.syrjala@linux.intel.com" title="Ville Syrjala <ville.syrjala@linux.intel.com>"> <span class="fn">Ville Syrjala</span></a>
</span></b>
<pre>(In reply to Maarten Lankhorst from <a href="show_bug.cgi?id=106804#c13">comment #13</a>)
<span class="quote">> Ah, that is the missing piece why it chooses that mode.
> X.org is borked and just sets doublescan/interlaced is always possible with
> modesetting:
> output->interlaceAllowed = TRUE;
> output->doubleScanAllowed = TRUE;
>
> And because it has the highest clock, you get your 1920 mode with
> doublescan..</span >
Also the mode flags aren't even checked by the xf86DefaulltModes stuff. So even
if we set doubleScanAllowed=FALSE we'd still get doublescan modes in the list
:(</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>