From: Larry Finger <Larry.Finger@lwfinger.net>
To: jerome huang <jerome.syno@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: rt8192cu on USB3
Date: Wed, 07 Mar 2012 20:35:36 -0600 [thread overview]
Message-ID: <4F581AF8.4080001@lwfinger.net> (raw)
In-Reply-To: <CAHaq0gLOPpDKazM0WPmkkOmJ1gR-vqOX9Q+J3nXArD5N0MgmMw@mail.gmail.com>
On 03/07/2012 08:16 PM, jerome huang wrote:
> log:
> [53614.238023] Compat-wireless backport release: compat-wireless-v3.2-1-s
> [53614.244729] Backport based on linux-stable.git v3.2
> [53614.368074] alg: No test for arc4 (arc4-generic)
> [53614.402781] cfg80211: Calling CRDA to update world regulatory domain
> [53614.498603] rtl8192cu 3-3:1.0: usb_probe_interface
> [53614.503552] rtl8192cu 3-3:1.0: usb_probe_interface - got id
> [53614.509920] rtl8192cu: rtl8192cu: Chip version 0x11
> [53615.359336] rtl8192cu: MAC address: 08:10:74:f1:a1:0f
> [53615.364575] rtl8192cu: Board Type 0
> [53615.400583] rtlwifi: rx_max_size 15360, rx_urb_num 8, in_ep 1
> [53615.408918] usbcore: registered new interface driver rtl8192cu
> [53652.483311] rtl8192cu: MAC auto ON okay!
> [53652.887348] rtl8192cu: Tx queue select: 0x05
> [53652.921326] rtl8192c_common: Loading firmware file rtlwifi/rtl8192cufw.bin
>
> And I'm sure the function rtl_block_fw_writeN is used for firmware uploading.
>
> On 8 March 2012 10:03, jerome huang<jerome.syno@gmail.com> wrote:
>> Hi,
>>
>> I found a problem just like in the older discussion "Question about
>> error from xhci-hcd",
>> there was a xhci error "no room on ep ring" when plugin rtl8192cu on USB3.
>> (it works on USB2)
>>
>> After applying Larry's patch "rtlwifi: rtl8192cu: Change firmware
>> upload to use block writes",
>> I still get the same error "no room on ep ring".
>>
>> But under the same compat-wireless version,
>> rt8712 works on USB3.
>>
>> Does anyone still encounter this problem after applying this patch?
>> or do I miss something/patches?
This problem is in the USB system, not in the wireless driver. Keep me as a Cc,
but send mail to Sarah Sharp <sarah.a.sharp@linux.intel.com> and
linux-usb@vger.kernel.org. They will tell you what debugging is needed.
The patch was an attempt to minimize the number of writes needed to upload the
firmware, but it had no effect; however, it was still a good change.
I'm confused about one statement you made. There is no rt8712 driver, but there
is one named r8712u; however, it controls a completely different device than
rtl8192cu. Do you have both devices?
Larry
next prev parent reply other threads:[~2012-03-08 2:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 2:03 rt8192cu on USB3 jerome huang
2012-03-08 2:16 ` jerome huang
2012-03-08 2:35 ` Larry Finger [this message]
2012-03-08 6:35 ` jerome huang
2012-03-08 7:06 ` Andiry Xu
2012-03-08 7:11 ` Andiry Xu
[not found] ` <2A76B9D36150BE4293842BC2FE8FF165016A31@SCYBEXDAG04.amd.com>
2012-03-08 10:32 ` jerome huang
2012-03-08 11:26 ` jerome huang
2012-03-08 17:56 ` Larry Finger
2012-03-09 3:28 ` jerome huang
2012-03-09 3:59 ` Larry Finger
2012-03-09 7:39 ` jerome huang
2012-03-09 15:04 ` Larry Finger
2012-03-09 16:02 ` jerome huang
2012-03-22 22:31 ` Sarah Sharp
2012-03-23 2:24 ` Larry Finger
2012-03-23 20:34 ` Sarah Sharp
2012-03-24 2:16 ` Richard Farina
2012-03-24 4:59 ` Larry Finger
2012-04-05 22:49 ` Sarah Sharp
2012-03-24 4:55 ` 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=4F581AF8.4080001@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jerome.syno@gmail.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.