Quote:
|
Originally Posted by CommanderROR
That makes the total uptime around 15:30 hours. Not really great, but a nice improvement over the standard configuration.
|
Well, it this would be close to doubleing my runtime and would mean that I would not run out of battery during the day. Of course it's still far from leaving your travel-dock at home during holidays. Though it would be possible displaywise, I'm absolutely sure that it's not possible hardwarewise because somebody completely fscked up the hardwaredesign there.
Quote:
|
Originally Posted by CommanderROR
The next steps now would be to add voltage scaling and of course link the script into the iPDF launch.
|
The script is only meant as a comfortable way of testing runtime at different CPU speed. Please don't expect me to try integrating it into the launcing process of the viewers, I don't need a bricked iLiad, so this is exactly the area of the device I'll stay away from.
Apart from that I think that the best place (quickest win) to take advantage of frequency scaling would be iPDF. Give it a config-file in ~/ , do set min-speed and max-speed and make it set speed to min-speed if rendering is completed and set it to max-speed during rendering. min-speed and max-speed can be set to the same values if you don't like speeding up.
The config-file could be set up comfortably using a script that reads and writes the parameters in manifest.xml, similar to my script. So we would not need an additional GUI element for iPDF.
And then hope that iRex somehow adapts the battery indicator.
Quote:
|
Originally Posted by CommanderROR
Turning pages at 30Mhz is absolutely OK, no need to scale the processor up again.
|
I have to disagree here. I have some documents where 33 MHz are sufficient and then some complex documents that render too slowly. Maybe having iPDF not only read ~/.ipdfrc but even $DOCUMENTFOLDER/.ipdfrc would be a good and very simple idea. By this one could override the standard behaviour by placing a different setup in the folder of the document to open...
Quote:
|
Originally Posted by CommanderROR
I don't know anything about programming, but there seem to be lots of websites with information about implementing powersaving for PXA255
|
I'm sure the iRex people have all the information but somehow (were) decided that powersaving by frequency scaling is not worth the effort. And they would have been right if they were capable of sending the system to deep-sleep and waking it up on button interrupts...
#!chris