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:32:00 +0000 [thread overview]
Message-ID: <1467793848.3086.37.camel@synopsys.com> (raw)
In-Reply-To: <577CC035.1000404@de.bosch.com>
Hi?Oleksij,
On Wed, 2016-07-06 at 10:24 +0200, fixed-term.Oleksij.Rempel wrote:
>?
> Hm... this Endpoint should be Interrupt, not Bulk. If you search for
> lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.
>
> what did went wrong here? Is it not working in USB High Speed mode?
Unfortunately as of now on that board EHCI doesn't work.
That's not a problem of a particular USB device but something in either
ECHI host controller or its integration. I do hope we will fix it sometime soon
(this is a development board and USB controller is implemented in FPGA so
there's a chance to fix stuff later on).
So given only OHCI works on the board I went forward and attempted to use it
with Wi-Fi USB dongle.
-Alexey
WARNING: multiple messages have this Message-ID (diff)
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: ath9k-htc on OHCI -> bogus usb xfer
Date: Wed, 6 Jul 2016 08:32:00 +0000 [thread overview]
Message-ID: <1467793848.3086.37.camel@synopsys.com> (raw)
In-Reply-To: <577CC035.1000404@de.bosch.com>
Hi?Oleksij,
On Wed, 2016-07-06@10:24 +0200, fixed-term.Oleksij.Rempel wrote:
>?
> Hm... this Endpoint should be Interrupt, not Bulk. If you search for
> lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.
>
> what did went wrong here? Is it not working in USB High Speed mode?
Unfortunately as of now on that board EHCI doesn't work.
That's not a problem of a particular USB device but something in either
ECHI host controller or its integration. I do hope we will fix it sometime soon
(this is a development board and USB controller is implemented in FPGA so
there's a chance to fix stuff later on).
So given only OHCI works on the board I went forward and attempted to use it
with Wi-Fi USB dongle.
-Alexey
WARNING: multiple messages have this Message-ID (diff)
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "fixed-term.Oleksij.Rempel@de.bosch.com"
<fixed-term.Oleksij.Rempel@de.bosch.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"anders.darander@gmail.com" <anders.darander@gmail.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux@rempel-privat.de" <linux@rempel-privat.de>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: ath9k-htc on OHCI -> bogus usb xfer
Date: Wed, 6 Jul 2016 08:32:00 +0000 [thread overview]
Message-ID: <1467793848.3086.37.camel@synopsys.com> (raw)
In-Reply-To: <577CC035.1000404@de.bosch.com>
Hi Oleksij,
On Wed, 2016-07-06 at 10:24 +0200, fixed-term.Oleksij.Rempel wrote:
>
> Hm... this Endpoint should be Interrupt, not Bulk. If you search for
> lsusb of this kind of adapter all of them list EP3 and EP4 as Interrupt.
>
> what did went wrong here? Is it not working in USB High Speed mode?
Unfortunately as of now on that board EHCI doesn't work.
That's not a problem of a particular USB device but something in either
ECHI host controller or its integration. I do hope we will fix it sometime soon
(this is a development board and USB controller is implemented in FPGA so
there's a chance to fix stuff later on).
So given only OHCI works on the board I went forward and attempted to use it
with Wi-Fi USB dongle.
-Alexey
next prev parent reply other threads:[~2016-07-06 8:32 UTC|newest]
Thread overview: 35+ 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 12:20 ` Alexey Brodkin
2016-07-05 12:20 ` Alexey Brodkin
2016-07-05 17:23 ` [ath9k-devel] " Oleksij Rempel
2016-07-05 17:23 ` Oleksij Rempel
2016-07-05 17:23 ` Oleksij Rempel
2016-07-05 17:31 ` [ath9k-devel] " Alexey Brodkin
2016-07-05 17:31 ` Alexey Brodkin
2016-07-05 17:31 ` Alexey Brodkin
2016-07-05 19:01 ` [ath9k-devel] " Oleksij Rempel
2016-07-05 19:01 ` Oleksij Rempel
2016-07-05 19:01 ` Oleksij Rempel
2016-07-06 7:44 ` [ath9k-devel] " Alexey Brodkin
2016-07-06 7:44 ` Alexey Brodkin
2016-07-06 7:44 ` Alexey Brodkin
2016-07-06 8:24 ` fixed-term.Oleksij.Rempel
2016-07-06 8:30 ` [ath9k-devel] " fixed-term.Oleksij.Rempel
2016-07-06 8:32 ` Alexey Brodkin [this message]
2016-07-06 8:32 ` Alexey Brodkin
2016-07-06 8:32 ` Alexey Brodkin
2016-07-06 8:38 ` fixed-term.Oleksij.Rempel
2016-07-06 8:39 ` [ath9k-devel] " fixed-term.Oleksij.Rempel
2016-07-06 8:45 ` Alexey Brodkin
2016-07-06 8:45 ` Alexey Brodkin
2016-07-06 8:45 ` Alexey Brodkin
2016-07-06 9:09 ` fixed-term.Oleksij.Rempel
2016-07-06 9:09 ` [ath9k-devel] " fixed-term.Oleksij.Rempel
2016-07-06 9:30 ` Alexey Brodkin
2016-07-06 9:30 ` Alexey Brodkin
2016-07-06 9:30 ` Alexey Brodkin
2016-07-06 10:32 ` fixed-term.Oleksij.Rempel
2016-07-06 10:32 ` [ath9k-devel] " fixed-term.Oleksij.Rempel
2016-07-07 5:16 ` Alexey Brodkin
2016-07-07 5:16 ` Alexey Brodkin
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=1467793848.3086.37.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.