[Changed the CC: list and the Subject to be more appropriate] On Mon, 11 Jan 2010, Clemens Fruhwirth wrote: > On Mon, Jan 11, 2010 at 4:15 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > On Sun, 10 Jan 2010, Rafael J. Wysocki wrote: > > > >> Bug-Entry   : http://bugzilla.kernel.org/show_bug.cgi?id=14841 > >> Subject    : unable to enumerate USB device on port X after suspend/resume > >> Submitter   : Fruhwirth Clemens <clemens@xxxxxxxxxxxxx> > >> Date      : 2009-12-19 11:45 (23 days old) > > > > This bug has been resolved as WILL NOT FIX.  It ended up having nothing > > to do with suspend or resume, it was caused by strange behavior in the > > device hardware. > > Should we track "automatic fallback to USB 1.1" as feature request? > You already said that this isn't easily possible with the way the USB > stack is structured at the moment (connect-centric-view instead of > port-centric-view). However, Windows does that fallback and I'm afraid > that this is the default device testing scenario. It can be done. The question is how should it work? That is, under what conditions should a new connection be forced immediately to full speed, and under what conditions should this behavior stop occurring? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
