Alan Stern wrote: > There are at least three problems that I can see. First, the device > doesn't disconnect from and reconnect to the USB bus when it starts > using new firmware. Yes, ath9k_htc has this problem. > Second, the device loses its firmware when it is > reset. Agreed again, this is a problem with ath9k_htc. > 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 ? Sujith -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
