W dniu 3 czerwca 2009 18:30 użytkownik Matthias Hopf
On May 22, 09 10:16:46 +0200, Rafał Miłecki wrote:
Interesting. Can you explain me something? Let's say my memory default clock is 800'000. I call RHDSetMemoryClock(400000); and then RHDGetMemoryClock(); which returns 400000.
Is this possible that my memory clock is still at 800000 if setting was called in wrong moment?
No, but chances are that the SetMemoryClock() could crash the system when called when the chip is not idle.
For very fast test I pushed following code: RHDGetMemoryClock(rhdPtr); RHDSetMemoryClock(rhdPtr, 400000 + (level * 1000)); RHDGetMemoryClock(rhdPtr); at end of static void DigLVDSSetBacklight(...) function. I can change memory clock without any problems and it seems to really work: (II) RADEONHD(0): Current Memory Clock: 495000 (II) RADEONHD(0): Attempting to set Memory Clock to 600000 (II) RADEONHD(0): Current Memory Clock: 594000 (II) RADEONHD(0): Current Memory Clock: 594000 (II) RADEONHD(0): Attempting to set Memory Clock to 540000 (II) RADEONHD(0): Current Memory Clock: 540000 (II) RADEONHD(0): Current Memory Clock: 540000 (II) RADEONHD(0): Attempting to set Memory Clock to 560000 (II) RADEONHD(0): Current Memory Clock: 558000 (II) RADEONHD(0): Current Memory Clock: 558000 (II) RADEONHD(0): Attempting to set Memory Clock to 580000 (II) RADEONHD(0): Current Memory Clock: 576000 Don't know if it is just my AtomBIOS that idles everything needed itself, or what, but it works. Tested even with Xv playing. Is this possible that some other AtomBIOSes don't idle needed blocks and this will hang X/GPU? -- Rafał Miłecki -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org