View Single Post
Old 03-11-2007, 02:38 PM   #81
CommanderROR
eink fanatic
CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.CommanderROR is fluent in JavaScript as well as Klingon.
 
CommanderROR's Avatar
 
Posts: 2,022
Karma: 4924
Join Date: Mar 2006
Location: Germany
Device: STAReBOOK, iRex Iliad, Sony 505, Kindle 2
As we just found out in the developer section, CPU scaling alone (without other power saving and without voltage-scaling the CPU) let's the current Iliad beat the 15 hours mark. This was done with a very simple script done by k2r.

Why has iRex not managed to implement even this "minimal" soultion after more than a year of Software development for the Iliad? Scaling is even a feature that is built into the PXA255 XScale processors, so it should be a pretty obvious thing to implement and it does give a very nice boost in battery-life (as we can now see...). Voltage scaling should help things along even more.
If you can't do suspend (and it has been obvious that the Iliad can't for a while now) then you should be grasping for straws like that like a drowning man...I just don't get the development philosophy at iRex...it should not take more than a few hours of programming to get voltage and frequency scaling up and running...at least as far as a non-programmer like me can judge...
CommanderROR is offline   Reply With Quote