Am Mittwoch, 25. November 2009 16:16:32 schrieb Rickard Bellini: > I think you are on to something here. Testing the last correction below, > and including the extra msleep(50); before the usb_mark_last_busy(udev); > in the remote_wakeup() function within hub.c. I have not seen any XactErr > or USB resets triggered by remote wakeup in over 5000 cycles. I will need > to keep running until I hit something around 10000 cycles until I can > judge it stable. Hello, this looks good. I am afraid you will have to determine a sensible timeout. 200ms is an outrageous time for this and hopefully much too long. Then we'll have to add a quirk for your device. Regards Oliver -- 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
