Hi David, Alan !
What exactly changed in the recent USB stacks that is causing it to
abort system suspend much more often ? I'm getting lots of user reports
with 2.6.15-rc5 saying that they can't put their internal laptops to
sleep, apparently because a driver doesn't have a suspend method
(internal bluetooth in this case).
It's never been mandatory so far for all drivers of all connected
devices to have a suspend method... didn't we decide back then that
disconneting those was the right way to go ?
Any reason we are rejecting the sleep process for these currently ? A
locking issue that makes disconnecting not yet feasible ? What changed
from the previous version where that worked ?
Cheers,
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
