Quote:
Originally Posted by NullNix
This just suggests that the battery circuit had not yet fully calibrated itself: its initial assumption was that the battery had less capacity (or rather, a higher minimum voltage / internal resistance) than it in fact did. It should be better calibrated now a full discharge has happened.
|
The results of this second run seem to bear that out (no weird "pauses" in the reported discharge curve).
Quote:
Originally Posted by knc1
Now, install my CPU Report, KUAL extension -
it has menu entries to select the various cpu governors.
as I recall, the K5 has an additional governor setting for which there is no button - but run the report, that will tell for sure.
What is for certain not documented is the 'user space' governor.
Which is most likely the one you want to use in this application.
That would let your application set the lowest speed/power setting as it enters its wait period, and then set the highest speed/power setting the first thing after waking up.
That can be a last refinement after you have your application working as desired.
|
That's a great idea. Thank you! I have experimented with some things in "/sys/devices/system/cpu/cpu0" and do have the extra governor setting. I did notice that depending on the governor selected I sometimes couldn't adjust frequencies, and sometimes had extra info available in that virtual filesystem area. Is any of that stuff documented somewhere is your KUAL extension code the best spot to look? (I confess that I haven't installed it yet to see if it adjusts files there or uses a LIPC call or what).