<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69721#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Can't reach maximum memory speed (or core speed) when using dpm=1 on r600g on cards not sticking to reference board"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69721">bug 69721</a>
from <span class="vcard"><a class="email" href="mailto:agd5f@yahoo.com" title="Alex Deucher <agd5f@yahoo.com>"> <span class="fn">Alex Deucher</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=69721#c4">comment #4</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=69721#c3">comment #3</a>)
> > Did you try again after fixing the vddci setup?
>
> To my knowledge, the memory speed is still limited to 1250 instead of
> reaching its maximum speed of 1300; the same thing goes for the core clock.
> I'll need to have a look at the code, but the last time I had a look, we
> were still calling btc_get_max_clock_from_voltage_dependency_table(), which
> was limiting the speed to the reference values.</span >
Right. I mean have you tried reverting that patch or just skipping the calls
to btc_get_max_clock_from_voltage_dependency_table(). I think they should work
fine now that vddci is fixed.</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>