> > Impossible to give generally. The answer would be a matrix of power
> > state and ability to do a remote wakeup.
>
> To keep it simple, we can simply report whether the device supports remote
> wakeup at all, in any state. If the user wants remote wakeup enabled but
> the system institutes a policy where the power level doesn't allow the
> device to do wakeup, the driver can either report an error or just ignore
> the problem and leave wakeup disabled.
Then where is the benefit? You could just let the user try it and fail/ignore
it.
Regards
Oliver
-------------------------------------------------------
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