On 8 March 2012 18:32, jerome huang <jerome.syno@xxxxxxxxx> wrote: > On 8 March 2012 15:23, Xu, Andiry <Andiry.Xu@xxxxxxx> wrote: >> I don't know why my email is mangled so I remove all the receivers. >> Please reply the mail adding Larry, Sarah and USB list. >> >>> -----Original Message----- >>> From: Andiry Xu [mailto:andiry.xu@xxxxxxx] >>> Sent: Thursday, March 08, 2012 3:12 PM >>> To: jerome huang >>> Cc: Larry Finger; linux-wireless@xxxxxxxxxxxxxxx; Sarah Sharp; linux- >>> usb@xxxxxxxxxxxxxxx >>> Subject: Re: rt8192cu on USB3 >>> >>> On 03/08/2012 02:35 PM, jerome huang wrote: >>> > >>> > I also tried to slow down between each write during firmware upload, >>> > and enlarge the ring size in xhci_endpoint_init(), >>> > but it seems that the trbs in the ring are not processed and >>> > the incoming trb is always queued till ring full. >>> > >>> >> >> This is interesting thing. How do you find out the trbs in the ring are >> not processed? Do you see handle_tx_event() triggers and urbs are >> givenback in the irq handler? >> >> There is a new version of ring expansion patchset: >> >> www.spinics.net/lists/linux-usb/msg59391.html >> >> But I'm not sure if it helps in your case. if the trbs are continuously >> queued but without completion, ring expansion will loop until memory is >> depleted. >> >> Thanks, >> Andiry >> >> > > Hi all, > I tried to print more information for firmware upload, > and handle_tx_event is triggered and urbs are givenback. > > This time I found the first "no room on ep ring" > is before "Loading firmware file" (line 176) > and there is no error during firmware upload, > after firmware upload completion, > "no room on ep ring" appears continuously (line 264). > > So the problem is not in firmware upload, > but in the other place after firmware upload? > > Please let me know if you need other debug messages. > > BR, > Jerome Hi all, I found a interesting thing. Here is my original test steps: 1. plugin 8192 => at this step, modules will be inserted 2. ifconfig wlan0 up => at this step, firmware will be uploaded 3. iwlist wlan0 scanning => check if wlan0 works The original problem occurs at last step, there is "always" no ap list result. And I found a way to make it work "always": 1. plugin 8192 2. ifconfig wlan0 up 3. ifconfig wlan0 down 4. ifconfig wlan0 up 5. iwlist wlan0 scanning If I up->down->up sequentially, (without scanning after first up), and then scanning(step 5), it works! Does this mean the firmware is not transfered or written correctly? BR, Jerome -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
