<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76564#c36">Comment # 36</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [AMD Fusion E-350] HDMI refresh rates doesn't match expectations"
href="https://bugs.freedesktop.org/show_bug.cgi?id=76564">bug 76564</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=76564#c35">comment #35</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=76564#c34">comment #34</a>)
> > Why not increase the ref_div? hardware frying? That way you can get the
> > clock exactly right.
> >
> > For example: 148.5 = 100 * 29.7 / 4 * 5
> > 74.2 = 100 * 37.1 / 5 * 10
>
> Just noticed that the clock values shown by xrandr are already rounded. So
> the 74.2MHz for 23.976fps actually is 74.17MHz. This would mean the PLL can
> never exactly generate the clock that is requested by the television I guess.
>
> Perhaps something else is wrong with the PLL then</span >
The PLL is fine, you can't just represent some frequencies 100% correct.
I'm already digging into making more use of the ref divider, just give me some
time to get the algorithem straight.</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>