> If somebody would like to suggest a programming interface (a waitqueue > perhaps?) by which the USB hub driver could send a notification when it > becomes idle, I could implement it. I actually started the USB console stuff with exactly this approach, but switched to the approach that's out there. A minor drawback, which is probably obvious, is that you actually wait for some interval without getting anything to do before you think things are idle. But a bigger drawback is that you lose the ability to chose appropriate intervals for different classes of devices. So far, there appear to be three possible USB boot devices: consoles, network devices, and boot devices. A system may not have all of these and so may not need to wait as long as a system with all of them. One of my goals is to preserve as much of the reduction in boot time as possible, even on systems that use USB devices that may or may not be plugged in. > Alan Stern David VomLehn -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
