[ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer

Hi+AKA-Oleksij,

On Wed, 2016-07-06 at 10:38 +-0200, fixed-term.Oleksij.Rempel wrote:
+AD4- 
+AD4- On 06.07.2016 10:32, Alexey Brodkin wrote:
+AD4- +AD4- 
+AD4- +AD4- Hi Oleksij,
+AD4- +AD4- 
+AD4- +AD4- On Wed, 2016-07-06 at 10:24 +-0200, fixed-term.Oleksij.Rempel wrote:
+AD4- +AD4- +AD4- 
+AD4- +AD4- +AD4- +AKA-
+AD4- +AD4- +AD4- Hm... this Endpoint should be Interrupt, not Bulk. If you search for
+AD4- +AD4- +AD4- lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.
+AD4- +AD4- +AD4- 
+AD4- +AD4- +AD4- what did went wrong here? Is it not working in USB High Speed mode?
+AD4- +AD4- Unfortunately as of now on that board EHCI doesn't work.
+AD4- +AD4- 
+AD4- +AD4- That's not a problem of a particular USB device but something in either
+AD4- +AD4- ECHI host controller or its integration. I do hope we will fix it sometime soon
+AD4- +AD4- (this is a development board and USB controller is implemented in FPGA so
+AD4- +AD4- there's a chance to fix stuff later on).
+AD4- +AD4- 
+AD4- +AD4- So given only OHCI works on the board I went forward and attempted to use it
+AD4- +AD4- with Wi-Fi USB dongle.
+AD4-
+AD4- I did some tests for 2 years on OHCI controller on x86. There was no
+AD4- noticable issues. It was even a bit faster then Intels EHCI. I don't
+AD4- think OHCI alone is the source of this problem.

Well I was also surprised how well that dongle works with that board in
OHCI mode. I saw quite consistent +AH4-4-5 Mbit/second rates when doing Speedtest
from my smartphone. So IMHO it's completely usable. Especially on that kind of
HW which has main CPU running at just 100MHz.

+AD4- On other side, so far i know, this adapter claims to provide usb full
+AD4- speed support, (Not only high speed) and may use different usb
+AD4- descriptor for this. May be this is the problem.

So is there something we may do with all that?

-Alexey