-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jesse Barnes wrote:
> The other option is to calculate how many vblank interrupts have > occurred between off and on periods. You could do this by recording > the time when interrupts were disabled, figuring out how much time has > passed between then and when they become enabled again, then dividing > by the refresh rate. That should work in theory, but I don't think > anyone's tried to do this in practice yet. > > Doing the latter will keep interrupts off more of the time, so it should > save more power. Two issues with this plan occurred to me while I was doing the MGA port. 1. The kernel doesn't (currently) have any way to know what the refresh rate is. 2. Even if it did know the refresh rate, the refresh rate can change while vblank interrupts are disabled. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHKh45X1gOwKyEAw8RAnNSAJ47MPa06urPFt3D228TzPF5AASb2wCgnZEC WzYCh+WyUVfRtZUiOuO3iCo= =XbSF -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
