On Sun, 6 Jun 2010, Phil Dibowitz wrote: > On 05/19/2010 07:56 PM, Alan Stern wrote: > >>> I have no idea why it would do this. A firmware bug would generally > >>> cause it to die every time, but there's no other obvious explanation. > >>> Particularly since the alternate firmware does not die; it handles the > >>> request correctly. > >> > >> Hmmm. I guess I'll go read the PIC USB interface specification and see > >> how much of this is SW vs. HW controlled on this microcontroller. > > > > It's odd that this occurs only some of the time. Maybe it depends on > > some low-level timing details. > > Could this be something like the GET_IDENTITY problems we used to see, where > we just need to wait a bit before sending this? Maybe. I tend to doubt it, but it's certainly possible. And it's easy enough to test, by adding a delay in the appropriate place. That would mean putting something like msleep(1000); at the start of the check_highspeed() routine in drivers/usb/core/hub.c. 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
