I'm interested in doing this myself.  I haven't actually timed it, but right now it seems to take our system (running gumstix overo summit pack) about 30 seconds to boot.  I could likely decrease the time somewhat by not having different services starting like ssh or broadcasting for a dhcp address.

As for power management, I haven't had much luck yet.  I read somewhere about running 'echo mem > /sys/power/state', but that seems to just immediately return to a prompt after displaying some messages that appeared to be simulating going to sleep when I run it.  I did notice that 'no apm support in kernel' does display on bootup, but don't know if apm is needed for ALL power management functions, or just more advanced ones.

On Thu, Apr 29, 2010 at 12:09 PM, Greg <gumstix@mosaicengineering.com> wrote:

I'm contemplating a battery-powered application, where an Overo would need to repeatedly place itself into a low-power standby state; typical usage would involve waking up the Overo (through a keypress or other sort of interrupt), running it for 30-60 seconds, and then placing it back into standby until the next usage.  So I'm having two questions:

1) Is anyone doing something similar, and finding it to work with a high level of reliability?

2) How long does it take for an Overo to boot, from a cold start (as opposed to from a standby state)?  My recollection from using a Verdex a couple of years ago, was that boot times were up around 60-90 seconds, which would be very long by comparison to what I'm needing now...



gumstix-users mailing list