Is there something that can be done to fix this?
Not sure; bus mastering is used for sending commands to the GPU when the
DRI is enabled (I wouldn't exactly call that 'pointless'...), but that
shouldn't be going on all the time, unless e.g. a client that rarely
(but regularly) redraws parts of its windows is enough to prevent the
CPU from entering C3? Either way, it would be very useful if you could
somehow determine exactly what the guilty bus mastering cycles do.
I think a clock or similar applet might do this - if it has to redraw
pictures it might use bus mastering to upload them.
Lorenzo - the reason for using bus mastering for this is that it really is
a few times faster than "regular" way.
best
Vladimir Dergachev
--
Earthling Michel D??nzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
