Alan Stern wrote:
On Wed, 22 Sep 2004, Oliver Neukum wrote:
I am sure the swsusp people will really appreciate the added
necessity to first compute the set of devices that need to run.
I've always been surprised they don't do that already. After all,
they have the swap device in hand; walk from there up to the root,
and there you go.
Left unsaid is how a suspended device can be woken up automatically when
it is needed. Presumably that would be handled by whoever put it to sleep
in the first place... And if you manually suspend a drive that contains a
swap partition, you get what you deserve! :-)
"Auto wakeup" comes up along with things like "veto suspend"
and "prepare, then commit": they're all notions about how to
deal with the fact that quiescing any complex system (prior
to suspend, or whatever) is basically a big "Whack-a-Mole"
game since there _will_ be cases where you have to backtrack
a bit, and wake something up, in order to progress the rest.
How could one identify situations where the system is refusing
to suspend, by re-activating parts of itself all the time?
If you want to design a model acceptable to all subsystems _and_
the core power management system, it needs to be simple above
all.
Make that: "as simple as possible, but no simpler"!
Unfortunately I only have a limited grasp of the issues involved, let
alone the special requirements of all the different subsystems...
I think if the model can handle USB well, that'd be progress even
if there were still be other things it needs to address.
- Dave
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
