Closed tjbp closed 5 years ago
This issue is caused by dwc2 driver or hardware. dwc2 is cheap ip core with different issues. Most of the functionality is implemented in software and make it not so performant in comparison to the controller which you will usually found on a x86_64 machine. One of huge issues of dwc2 is problem with mixed and fragmented transfers. Try to remove every thing else on the usb bus and test i again. In any case, it is not some what should be fixed by ath9k-htc driver or firmware
OK thanks, that's a fair enough explanation! Time to find a different platform...
Consistently under all circumstances when using a AR9271 dongle on a Raspberry Pi 3 (ARM) device, I receive the following:
Using the identical firmware with the same dongle on an x86_64 machine it works fine:
136 looks like the same issue but has since been closed. Interestingly it all describes hotplugging as working - I find nothing will work now, whether hotplugging or booting with the dongle attached.