Powering down is the easy part, sometimes the power company does that for me. Bringing it back up is the hard part. Having an excellent software architecture for power savings will help, but not as much as you would hope.

SoCs are incredibly black-box when you power devices and/or the CPU down. You have nothing to help you -- especially logs -- until you bring it back up. Often, even JTAG cannot attach depending on how deep it went. There are fewer signals leaving the SoC, so there's less to probe. You'll find yourself desperately grasping for any sign of life. If you guess wrong too often, you might even fry portions of the chip.

If they provide no documentation, it's even harder. Bringing it back up is all-or-nothing and you're at the mercy of the configuration and register sequences you did. If you do it wrong, you might introduce the internal bus to APIC #2: Destroyer of Worlds.

Sorry to focus so much on a bummer. If the Atom really is %25 efficient as ARM while running, these power cycles are important to compete with Windows over battery life.

Evolution isn't irrefutable. I can't stand hearing ID advocates saying ID is science, but "irrefutable" is something scientists can't claim. It's sort of like claiming your program has no bugs. Scientists only create models based on what they can observe, with a black-box mentality, reverse-engineering nature. To claim "irrefutable" requires you to know everything about how it works. Without asking some supernatural being, we never can...