From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer
Date: Wed, 6 Jul 2016 08:45:50 +0000 [thread overview]
Message-ID: <1467794679.3086.42.camel@synopsys.com> (raw)
In-Reply-To: <577CC3A2.5070607@de.bosch.com>
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
next prev parent reply other threads:[~2016-07-06 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 12:20 [ath9k-devel] ath9k-htc on OHCI -> bogus usb xfer Alexey Brodkin
2016-07-05 17:23 ` Oleksij Rempel
2016-07-05 17:31 ` Alexey Brodkin
2016-07-05 19:01 ` Oleksij Rempel
2016-07-06 7:44 ` Alexey Brodkin
2016-07-06 8:30 ` fixed-term.Oleksij.Rempel
2016-07-06 8:32 ` Alexey Brodkin
2016-07-06 8:39 ` fixed-term.Oleksij.Rempel
2016-07-06 8:45 ` Alexey Brodkin [this message]
2016-07-06 9:09 ` fixed-term.Oleksij.Rempel
2016-07-06 9:30 ` Alexey Brodkin
2016-07-06 10:32 ` fixed-term.Oleksij.Rempel
2016-07-07 5:16 ` Alexey Brodkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1467794679.3086.42.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).