click

poqako released sleep mode according to pdroms.

no explanation or docs tho - am scared.

anyone know anything?

??????!!!!

.... I don't think that will work....

There is not source code...
Select = sleep
Start = wake up

I think it just turns off the screen and sets low frequency (60Mhz?).

I think hibernate is more interesting

ah, ok. thought this sounded too good to be true.

still, could have its uses

Well, that's what I think, I cannot know since there isn't source code.

I'll try it if the coder says something about it.

Bump for sleep mode. Is anyone going to try this? Could be malicious code, but then again, why would anyone bother writing malicious code for GP2X?

"I'm not gonna try it ... YOU try it!!"

I'll wait to see if Mikey's GP2X blows up first ...

Because they saw everyone follow a sheep over the cliff with my DaveC image firmware. They can now see how easily a flash to the U-Boot could be tricked into being run. That would kill a gp2x without a Jtag.

True.

Indeed, it could be sleep or coma.
I'll pass for the moment.

Chimpoid

I've not run it, but loading it into my disassembler seems to suggest that it's an SDL application and it doesn't bother to try and attempt to access the hardware registers, so I'm not exactly sure what it's supposed to do.

Maybe it just draws the screen black and waits for a button sequence

I tried it. It doesnt do anything but display a black screen with the backlight still on? I am using oddbots 1.4

Even I could have done that.

Maybe it's more of a keyboard locker (as you have to press start+select to exit) rather than a program to reduce the power consumption of the gp2x ?

Something tells me that a program designed to reduce power consumption and simply put the gp2x into a 'sleep mode' shouldn't be 766KB, that's the first red flag right there. Even if it's not malicious, it's down right ridiculous! You can write a 20 lined program to turn the LCD off and poll the button states and turn the LCD back on.. why on earth do you need to statically link SDL to that?! Anyways, after I saw its filesize I went out to make my own little one .. but it seems that calling select() on /dev/GPIO doesn't work.. I'm a little confused on that. read() isn't blocked but select wont return with success. Perhaps I'll just step through fs/select.c later on.. but maybe someone knows something that I don't know regarding this?

do you seriously think someone would write malicious programs for the gp2x?, no one would do that here, its a nice community .

A black screen with backlight is on. Buttons are locked and when you press start and select the screen gets back on. Would be better if it could turn the backlight off.

Are we going to have a challenge to see who can get the gp2x to draw the least current?

If so, consider me in

It's PSPupdates back for revenge

Hmm, shut off TV encoder, stop the SD clock generator, turn the backlight off, reduce CPU clock to 60MHz, run a halt instruction on the CPU if possible (not too familiar with how ARM9 works there, but linux probably does it itself if the program yields its timeslice), shut off the LCD itself if it can...

Of course nothing would beat a good suspend-to-SD/NAND.

True, but if we can drop current consumption to something that means it'll last a week on a pair of nimh's, then it can't be bad

Hmmm, quick calculation tells me 15mA from some 2500mAh batteries would give something like 7 days usage. Anyone think it's possible to reduce the GP2X's current consumption that far?

Hmmm, the power LED probably draws about 10ma

Why you just dont turn your GP off?

Boot time =(

The only reason I still have 33 seconds boottime is because I am waiting for the next "homebrew"-fw release, then I'll probably have about 10 seconds, so who cares then? ;D
I hope craigx manages to get all that good stuff into the GPH-FW too ;D

I wouldn't call 9 seconds that bad

You will when you are dead.

Edit: I don't mean that in a creepy way.

?

Well well, Hans is going to hunt down and kill you Squidge.

Hopefully not before I finish my emu and shave some more seconds of the boottime

the 9 second boot time is with 3rd party firmware which locks the nand and causes some things to not even work, you shouldnt be using that as a argument, the official boot time is still around 40 seconds isnt it?

Meh, stuff that doesn't work is mostly stuff that is writing to nand, and they shouldn't be doing that anyway ;-P