On Wed, 9 Feb 2011, Sujith wrote: > > The first two problems are the device's fault, and the third is the > > driver's fault. None of them are the fault of usbcore. > > Indeed, which is why this dirty hack is done in the driver. > And it was done to fix a similar issue - high CPU usage when scanning. > > But do you have any suggestion for such broken devices ? > The FW changes the type from Interrupt to Bulk, but can the host > driver continue to use Interrupt URBs and use the URB_NO_INTERRUPT trick > that you have mentioned ? Yes. And it's not a trick; that is exactly what URB_NO_INTERRUPT was intended for. 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
