> >> Basically, we need to guarantee that on resume, all CURRENTLY > >> PLUGGED IN hardware gets initialised to a known state, and anything > >> short of that is just plain buggy. This includes the case where on > >> resume, devices are found plugged into different ports than on > >> suspend. > > > If you assume a Linux-USB system that's fully set up with the > > hotplugging tools, what functionality is missing? > > The words "If you assume" in the above state the problem quite clearly. > No such assumption can be made, and when you take that assumption out of > the equation, the above required guarantee falls straight in your lap.
That is, if you don't use the tools, they won't solve your problems. At that point, why are you complaining? The first issue is that you're not using the tools ... not that the problems aren't already solved. "Falls straight in your lap" is in this case an issue of not using the tools provided to solve this problem. On the other hand, if you answered my question by showing where some particular functionality is missing, that'd be a start. It's known as providing a bug report. Even better would be to provide simple patches that'll resolve the issue of any missing functionality, in a way that they can easily be merged into the ongoing work (2.4.current for now, and common distros). (And yes, this thread is completely offtopic, hasn't been related to firmware for ages, and more belongs on the linux-hotplug list...) - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
