<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [HSW] no Intel HDMI video output with kernel 4.4 and 4.9"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101302#c29">Comment # 29</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - [HSW] no Intel HDMI video output with kernel 4.4 and 4.9"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101302">bug 101302</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>8bpc vs. 12bpc eh? Which probably means there's a broken component somewhere in
the signal path. Could be the level shifters in the source, cable, dongle, or
the monitor itself.
The workaround I've been suggesting is to add a knob for the user to limit the
color depth. The problem for cases like this where there is no output (as
opposed to just glitchy output) is that a connector property would have to be
changed by the user blind. The alternatives would be to change the default to
8bpc, or add a modparam (or something like it) to force the 8bpc already when
the driver loads. Hmm. Maybe we should extend the "awesome" video= cmdline
syntax a bit?</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 QA Contact for the bug.</li>
</ul>
</body>
</html>