<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SKL][DP] HP Lap Dock external display with DisplayPort over USB Type-C input not properly detected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104054#c58">Comment # 58</a>
on <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [SKL][DP] HP Lap Dock external display with DisplayPort over USB Type-C input not properly detected"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104054">bug 104054</a>
from <span class="vcard"><a class="email" href="mailto:jerome.debretagne@gmail.com" title="Jérôme de Bretagne <jerome.debretagne@gmail.com>"> <span class="fn">Jérôme de Bretagne</span></a>
</span></b>
<pre>Hi Rodrigo, I did compile a more recent drm-tip a couple weeks ago at:
commit 29a41cf5dd10ee68873c16b67d6212b3bd470906
Author: Ville Syrjälä <<a href="mailto:ville.syrjala@linux.intel.com">ville.syrjala@linux.intel.com</a>>
Date: Wed Mar 6 22:18:58 2019 +0200
drm-tip: 2019y-03m-06d-20h-18m-08s UTC integration manifest
With some delay, I'm happy to report that the Lapdock has properly been
detected and switched to its native 1920x1080 @ 60Hz resolution for the very
first time ever, in the exact same hardware setup as originally reported in
this bug!
To avoid confusion, this is pure drm-tip above, no patches applied.
I have no idea what change(s) since kernel 4.18 could explain this new outcome.
If that's of interest to anyone, I could try to bissect back to find when it
started working, but it could take me quite a while.
The monitor detection seems stable and reproducible during my tests today,
doing many unplug/replug checks ... as long as I keep the default relative
positioning of my 2 monitors. However, if I try to change the position of this
Lapdock screen next to my main one using the Gnome display settings (from the
right side to the left side for instance), my 2 screens blinks several times
for a few seconds and Gnome finally reverts to the previous known working
config. This is a different issue though.</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 on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>