From: Larry Finger <Larry.Finger@lwfinger.net>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, Joshua.Roys@gtri.gatech.edu
Subject: Re: [RFC] rtlwifi: fix in_ep = in_ep_num mishap in _rtl_usb_init_rx
Date: Mon, 15 Oct 2012 10:13:39 -0500 [thread overview]
Message-ID: <507C2823.7030500@lwfinger.net> (raw)
In-Reply-To: <201210151242.58431.chunkeey@googlemail.com>
On 10/15/2012 05:42 AM, Christian Lamparter wrote:
> It's a bit weird that you have three IN and OUT 0x3 eps. Is this
> really true or is this a c&p error and your devices have more
> than one interface configuration?
>
> The endpoint configuration for my SU devices (both are the same)
> look like this:
> Interface Descriptor:
> bEndpointAddress 0x83 EP 3 IN Bulk Data 512 bytes
> bEndpointAddress 0x04 EP 4 OUT Bulk Data 512 bytes
> bEndpointAddress 0x06 EP 6 OUT Bulk Data 512 bytes
> bEndpointAddress 0x0d EP 13 OUT Bulk Data 512 bytes
>
> It looks like that we should parse the endpoint descriptor and
> get the first endpoint from there.
The confusion arose from me reporting the EP configuration for the USB Bluetooth
component of an RTL8723AE that I currently have installed. It has the
bidirectional EPs:
bEndpointAddress 0x81 EP 1 IN
bEndpointAddress 0x02 EP 2 OUT
bEndpointAddress 0x82 EP 2 IN
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x83 EP 3 IN
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x83 EP 3 IN
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x83 EP 3 IN
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x83 EP 3 IN
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x83 EP 3 IN
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x83 EP 3 IN
My RTL8191SU and the RTL8192SU both have the following:
bEndpointAddress 0x83 EP 3 IN
bEndpointAddress 0x04 EP 4 OUT
bEndpointAddress 0x06 EP 6 OUT
bEndpointAddress 0x0d EP 13 OUT
My two copies if RTL8188CUS chips that use rtl8192cu both have
bEndpointAddress 0x81 EP 1 IN
bEndpointAddress 0x02 EP 2 OUT
bEndpointAddress 0x03 EP 3 OUT
bEndpointAddress 0x84 EP 4 IN
Although these chips have two IN EPs, the first is the one in use, thus
searching for the first IN EP should be OK, and we can ignore the fact that the
chip has two IN EPs. I am currently trying to acquire a sample of the RTL8192DU
device with dual band operation on separate MACs. I think it registers as two
separate devices (at least the PCI version does), and it should not change the
situation. Even if it does, its initial driver will be in staging, and will not
use rtlwifi.
Larry
prev parent reply other threads:[~2012-10-15 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 20:13 [RFC] rtlwifi: fix in_ep = in_ep_num mishap in _rtl_usb_init_rx Christian Lamparter
2012-10-14 23:38 ` Larry Finger
2012-10-15 10:42 ` Christian Lamparter
2012-10-15 15:13 ` Larry Finger [this message]
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=507C2823.7030500@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Joshua.Roys@gtri.gatech.edu \
--cc=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.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).