Mailinglist Archive: radeonhd (427 mails)

[Yang Zhao <yang@xxxxxxxxxx>]

2009/5/19 Rafał Miłecki <zajec5@xxxxxxxxx>:
> 1) Switched to VT1, then VT7, then grep-ped Xorg.0.log
> (II) RADEONHD(0): Just entered VT, clock is now at 168750Hz
>
> 2) Switched to VT1, then VT7, then grep-ped Xorg.0.log
> (II) RADEONHD(0): Just entered VT, clock is now at 168750Hz
>
> 3) Switched to VT1, then VT7, then grep-ped Xorg.0.log
> (II) RADEONHD(0): Just entered VT, clock is now at 168750Hz
>
> 4) s2ram (for my machine it uses -p -m), then grep-ped Xorg.0.log
> (II) RADEONHD(0): Just entered VT, clock is now at 675000Hz
>
> 5) Switched to VT1, then VT7, then grep-ped Xorg.0.log
> (II) RADEONHD(0): Just entered VT, clock is now at 675000Hz
>
> It's actually weird for me that you don't lose engine clock on
> suspend&resume. While machine is in suspend mode, only RAM should be
> powered, right? That would mean GPU doesn't get power and all
> registers are resetted to default values. Maybe suspending on your
> machine is broken? Maybe your GPU is still powered?

The kernel causes a VT switch to happen on suspend.

You can pull my xrandr code from
http://yangman.ca/git/xf86-video-radeonhd/ branch randr-pm


-- 
Yang Zhao
http://yangman.ca
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx