<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> <span class="fn">Christian König</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - 24P playback video signal loss with latest DRI patches"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77009">bug 77009</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;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - 24P playback video signal loss with latest DRI patches"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77009#c30">Comment # 30</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - 24P playback video signal loss with latest DRI patches"
href="https://bugs.freedesktop.org/show_bug.cgi?id=77009">bug 77009</a>
from <span class="vcard"><a class="email" href="mailto:deathsimple@vodafone.de" title="Christian König <deathsimple@vodafone.de>"> <span class="fn">Christian König</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=77009#c29">comment #29</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=77009#c28">comment #28</a>)
> 1) Run a setup program each time a hardware change is detected. (EDID or GPU)
> 2) Test LCD/Panel at various popular refresh rates.
> a) crank up the pll with your new algo.
> >> *test* if tv accepted it. (requires a knowledge of protocol to
> check display state, or have user answer ok with a timeout in case it is not
> readable)</span >
Well, that's way to much user interaction for this topic cause there is no way
to ask a TV if the picture looks ok other than asking the user.
I'm going to supmit the patch to drm-fixes (with a bit higher limit) so it
should end up in 3.15 together with the patch that created the problem in the
first place.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>