http://bugs.freedesktop.org/show_bug.cgi?id=26347
--- Comment #13 from Rafał Miłecki <zaj...@gmail.com> 2010-03-03 14:43:43 PST --- (In reply to comment #11) > I don't have all details memorized, but the maximum GPU clock for this chip is > 500MHz and the AC power state has both 500MHz and 330MHz CPU clocks. > The battery power state has 330MHz and 110MHz GPU clocks. It already shows driver uses at least 3 states. And you few lines earlier wrote: > But only state 1 and 2 are used by the Windows driver, > state 0 and 3 are never used. Anyway, I don't think it's really important to understand Windows driver. We may eventually need smarter reclocking algorithm. (In reply to comment #12) > Looking at the code in radeon_pm.c the current approach looks fundamentally > wrong to me: > > radeon_pm_set_clocks_locked seems to call radeon_set_power_state to issue > clock > changes. This just doesn't look right to me and is obviously not what the > Windows driver is doing. > > Or am I just misunderstanding the concept of power states? I guess you are. What does look incorrect for you in that? -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel