Re: [PATCH 2/2] Fix console handling during suspend/resume

[Jim Gettys <jg@laptop.org>]

We're building the OLPC machine in which the wireless hardware is alive
(and able to forward packets in the mesh) even with the machine STR.
Even our ATest hardware supports this for wireless.

Similarly for the screen; it can be "alive" while the machine is STR.
The power savings are dramatic. the screen takes an ASIC we don't have
back yet, so that we won't have until the next batch of boards.  And
with the Geode's UMA, all we should have to do on the console is save
and restore the graphics registers, which should be very fast.

The Wireless chip can wake the processor if it detects a packet bound
for that machine, rather than just being forwarded.  As far as other
machines are concerned, the destination machine can be considered
"alive" and not STR.
                         Regards,
                            - Jim


On Fri, 2006-06-23 at 12:23 -0700, Linus Torvalds wrote:

> 
> Network devices tend to do things like "unregister from the network stack" 
> etc, all of which should be totally unnecessary for STR. It's all there 
> really for _disk_ suspend, to make things quiet.
> 
> So the whole argument that "suspend()" is the minimal functionality is 
> just totally bogus. Its' simply not _true_. The current suspend() 
> functions do lots of things that have nothing to do with actual device 
> suspend, exactly because the current setup forces them to do so, not 
> because they would actually _need_ to do so for STR.
> 
> 			Linus
> _______________________________________________
> linux-pm mailing list
> linux-pm@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/linux-pm
-- 
Jim Gettys
One Laptop Per Child