#113942 - doynax - Mon Jan 01, 2007 3:32 pm
I'm working on a small book reader application for the GBA. And, yes, I'm aware of the one from Crowe Workshop, but it's got all sorts of small annoyances and limitations.
Perhaps not so surprisingly one of my main goals is to conserve as much battery power as much as possible.
Optimizing the code and letting the CPU sleep whenever possible as well as shutting down any unused hardware units seems obvious. But beyond that should I be aware of any useful tricks (say, place things in any particular type of memory, display the text in white-on-black rather than black-on-white, or use some odd graphics mode) or is it all diminishing returns after doing the basics?
(Note that attempting to measure things empirically won't be much of an option on my three year old SP with an already half dead battery.)
Anyway, thanks in advance for your input. And in the unlikely event that I actually manage to finish something this time around I promise to publish the source.
Perhaps not so surprisingly one of my main goals is to conserve as much battery power as much as possible.
Optimizing the code and letting the CPU sleep whenever possible as well as shutting down any unused hardware units seems obvious. But beyond that should I be aware of any useful tricks (say, place things in any particular type of memory, display the text in white-on-black rather than black-on-white, or use some odd graphics mode) or is it all diminishing returns after doing the basics?
(Note that attempting to measure things empirically won't be much of an option on my three year old SP with an already half dead battery.)
Anyway, thanks in advance for your input. And in the unlikely event that I actually manage to finish something this time around I promise to publish the source.