Hi!
> > > ������The transitions to and from the device-idle states needed for
> > > ������suspend-to-disk aren't well defined.
> >
> > I'll answer questions if you promise to submit documentation patch
> > ;-)). device-idle states needs to ensure:
>
> If I know what to write I'll write it.
Great, feel free to ask.
> > * no DMA running
> > * even if kernel state is lost, you are able to bring device back to
> > normal state... Or "when one kernel is replaced with another one, all
> > variables are lost, you still can resume that device". Easily
> > accomplished by having just one hardware state you put it into.
>
> OK. So to you don't actually care about the power state devices are in here
>
> device_power_down(3);
> is_problem = suspend_prepare_image();
> device_power_up();
> spin_unlock_irq(&suspend_pagedir_lock);
>
> You just want them to be quiet and have all state in ram. Is that
> right?
Yes, if system_state == SYSTEM_SNAPSHOT, I need all state ram and
devices quiet.
> In fact, actually switching devices off here would be bad, would it?
Well, you can switch the devices off here, if you want to. It will
only make things slower. [Well, devices that are really off
automatically _are_ quiet and have no state, so if someone does not
know about SYSTEM_SNAPSHOT, he should still do the right thing]
linux-devel does not exist on harward. I think original author meant
linux-usb-devel?
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-------------------------------------------------------
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
