<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> <span class="fn">Imre Deak</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT] igt@i915_module_reload@.*|igt@i915_pm_rpm@module-reload - dmesg-warn - *ERROR* VBT incorrectly claims port D is not TypeC legacy"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110595">bug 110595</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>imre.deak@intel.com, jani.nikula@intel.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT] igt@i915_module_reload@.*|igt@i915_pm_rpm@module-reload - dmesg-warn - *ERROR* VBT incorrectly claims port D is not TypeC legacy"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110595#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][BAT] igt@i915_module_reload@.*|igt@i915_pm_rpm@module-reload - dmesg-warn - *ERROR* VBT incorrectly claims port D is not TypeC legacy"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110595">bug 110595</a>
from <span class="vcard"><a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> <span class="fn">Imre Deak</span></a>
</span></b>
<pre>Martin, Jani,
there is no user noticeable consequence of the issue as far as I can think of.
The only effect of it is internal to the driver in that it has to delay
switching the port into legacy mode until the user plugs in a display (whereas
normally we would switch the port into legacy mode right at module loading).
I would still prefer keeping this as a DRM_ERROR - at least for now, since it
forces on us a complexity (delaying the switch) with the potential for bugs. So
I'd like the BIOS team to take this issue seriously and that we don't lose
track of it. I'm also wondering if it's better to keep the error log level even
for later so that we catch faulty OEM BIOSes easier even then.
Eventually - if we decide that keeping this bug open for reference isn't worth
it - we may give up as in the past with BIOS/VBT problems and tune down the
message even more as Daniel suggested. Let's wait and hope still for a while.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>