MobileRead Forums - View Single Post

jharker · 11-11-2007, 12:27 AM

Rincewind's original "powersave" ipdf implemented exactly this kind of CPU underclocking to save power.

Before releasing any "official" CPU scaling for the iLiad, iRex had to solve several kernel driver instability problems. These were eventually resolved.

The latest official iRex iLiad software version 2.11 scales the CPU speed to save power all the time. The CPU scaling is (I believe) handled by the PowerMgr program.

In contrast, Rincewind's powersave ipdf provided power conservation only when the pdf viewer was running (of course).

I don't know what the lowest stable speed is. Rincewind's ipdf went down to 100 MHz. It's possible that the official iRex work takes it down to 33 MHz, but I don't know what it actually does.

Edit: Oh, silly me, the most recent post was a necro post. Most of this thread dates from a long time ago.

11-11-2007, 12:27 AM	#7
jharker Developer Posts: 345 Karma: 3473 Join Date: Apr 2007 Location: Brooklyn, NY, USA Device: iRex iLiad v1, Blackberry Tour, Kindle DX, iPad.	Rincewind's original "powersave" ipdf implemented exactly this kind of CPU underclocking to save power. Before releasing any "official" CPU scaling for the iLiad, iRex had to solve several kernel driver instability problems. These were eventually resolved. The latest official iRex iLiad software version 2.11 scales the CPU speed to save power all the time. The CPU scaling is (I believe) handled by the PowerMgr program. In contrast, Rincewind's powersave ipdf provided power conservation only when the pdf viewer was running (of course). I don't know what the lowest stable speed is. Rincewind's ipdf went down to 100 MHz. It's possible that the official iRex work takes it down to 33 MHz, but I don't know what it actually does. Edit: Oh, silly me, the most recent post was a necro post. Most of this thread dates from a long time ago.