<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [HSW] i915 only uses 165MHz for HDMI port"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98491#c16">Comment # 16</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [HSW] i915 only uses 165MHz for HDMI port"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98491">bug 98491</a>
from <span class="vcard"><a class="email" href="mailto:karolherbst@gmail.com" title="Karol Herbst <karolherbst@gmail.com>"> <span class="fn">Karol Herbst</span></a>
</span></b>
<pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=98491#c15">comment #15</a>)
<span class="quote">> The original problem is that we detect your adapter as type 1 DP dual mode
> adapter, which are notoriously bad about reporting their max clock. Trying
> to read it from the adapter would result in more failures and black screens
> than what it would solve. Thus we limit to 165 MHz on type 1 adapters.
>
> Bit 11 of the VBT device class does seem to indicate HDMI rather than DVI
> output, but I am really not sure if that can be universally trusted.
> Something to think about though.
>
> Have you tried kernel v4.10 or later? It does have some fixes for certain
> types of adapters.</span >
not yet, will do when I can access the display again, which is at eastern the
latest.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>