| Summary: | Radeon VBlanks enabled after VT switch | ||||||
|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Arthur Taylor <art> | ||||
| Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||
| Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
| Severity: | minor | ||||||
| Priority: | medium | CC: | jkohen | ||||
| Version: | unspecified | ||||||
| Hardware: | x86 (IA32) | ||||||
| OS: | Linux (All) | ||||||
| Whiteboard: | |||||||
| i915 platform: | i915 features: | ||||||
| Attachments: |
|
||||||
|
Description
Arthur Taylor
2007-12-11 18:09:10 UTC
Created attachment 13049 [details] [review] disabe-vblank-on-entervt Testing on my hardware showed (Radeon Mobility M7 LW AGP) showed that enabling vblanks is not necessary, if a dri app was open during a vt switch it will call RADEONDRISetVBlankInterrupt when it is restored after the VT switch anyways. Furthermore, I found that after returning to xserver, even if RADEONDRISetVBlankInterrupt had never been called that vblanks were enabled as radeon@pci:0000:01:00.0 was generating 60 interrupts / second. It seems that RADEONDRISetVBlankInterrupt (pScrn, FALSE) can successfully be called in RADEONEnterVT, disabling vblanks and saving power while not effecting dri apps that may have been open, but of course I have no idea if this is true on other setups. *** Bug 13613 has been marked as a duplicate of this bug. *** fixed in commit: 6ccf5b33d27218ae1c45ab93c122438ed536d8ba |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.