<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c6">Comment # 6</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 <a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> Alexandre Demers</a> <pre>(In reply to <a href="show_bug.cgi?id=69721#c5">comment #5</a>) > (In reply to <a href="show_bug.cgi?id=69721#c4">comment #4</a>) > > (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. > > 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. Well that was one of the plans. ;) I'll try it later and let you know.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>