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: Sun, 14 Oct 2012 18:38:13 -0500 [thread overview]
Message-ID: <507B4CE5.2020104@lwfinger.net> (raw)
In-Reply-To: <201210142213.56197.chunkeey@googlemail.com>
On 10/14/2012 03:13 PM, Christian Lamparter wrote:
> in_ep and in_ep_num should not be the same as
> a device can have a different in_ep than "1".
>
> Signed-off-by: Christian Lamparter <chunkeey@googlemail.com>
> ---
> Note:
> This patch is related to:
> "[PATCH 3/9] rtlwifi: fix the selection of the bulk in endpoint"
>
> However, it would be much better if we can get rid of
> in_ep_num and define an in_ep array so the rtlwifi
> frameworks knows which EPs to scan. But this could be
> "too much" of an overkill, so another solution would
> be to just have a single in_ep.
>
> Larry, do you know of any hardware which has two in endpoints?
The RTL8188CU has the following:
Bus 004 Device 002: ID 0bda:8723 Realtek Semiconductor Corp.
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
My SU device has the same layout. It seems that only EP 1 is used exclusively
for input operations.
Larry
next prev parent reply other threads:[~2012-10-14 23:38 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 [this message]
2012-10-15 10:42 ` Christian Lamparter
2012-10-15 15:13 ` Larry Finger
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=507B4CE5.2020104@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 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.