On Tuesday 03 July 2007, Alan Stern wrote: > In the end, we may be forced not to autosuspend keyboards and mice. > There are lots of problems. One is broken hardware, as we see here.
This is unfortunate, but I suspect you're right. We may need a userspace database of devices which are known not to be broken. Since it appears that typical el-cheapo testing regimes for USB products tend not to cover suspend/resume usefully ... perhaps because Microsoft doesn't use USB suspend much. > And ISTR Dave Brownell mentioning a mouse which claimed to support > remote wakeup but in fact did not. Yes, I have one of those. It was one of the things motivating the existence of the /sys/devices/.../power/wakeup attributes: we need to be able to work around broken hardware. - Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
