> To summarise, we can either have firmware handling in user > space or power management, but not both.
What specific devices that have this problem? They'd seem "broken". Are they important enough that they deserve to torque the USB subsystem in this way? Why are they discarding their firmware, when they've been sitting around with power applied? (If they haven't kept power, they are not resumable.) I don't recall a good response to my "don't expect such devices to resume, make them re-enumerate" suggestion. That doesn't torque things at all; we already know that the USB subsystem needs to support per-device suspend and resume processing. > In fact, no user space task should run until devices involved > in paging have resumed operation. Does Linux PM have hooks into the VM subsystem to expose such constraints? Some of this doesn't relate to USB at all. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
