>2010/11/4 Rajkumar Manoharan <Rajkumar.Manoharan@xxxxxxxxxxx>: >>>2010/11/2 Rajkumar Manoharan <Rajkumar.Manoharan@xxxxxxxxxxx>: >>>> From: Ming Lei <tom.leiming@xxxxxxxxx> >>>> >>>> Obviously, we should set the transfer type consitent with >>>> endpoint descriptor type to urb, this patch fixes the probe >>>> failure below: >>>> >>>>[ 8.018768] PM: Removing info for No Bus:1-2.2 >>>> [ 8.019470] usb 1-2.2: BOGUS urb xfer, pipe 3 != type 1 >>>> [ 8.031707] usb 1-2.2: ath9k_htc: Unable to allocate URBs >>>> [ 8.037506] ath9k_hif_usb: probe of 1-2.2:1.0 failed with error -22 >>>> [ 8.044250] usbcore: registered new interface driver ath9k_hif_usb >>>> >>>> NACK. To optimize CPU consumption and scan duration, HTC device firmwares >>>> were patched to change descriptor types of EP3 and EP4 from Interrupt to Bulk. >>>> After firmware download in initialization, endpoint descriptors got changed. >>>> Please use the latest firmwares from linux-firmware git tree. >>>> >>>> http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git;a=summary >>> >>>My card is UB91, so you means I should update to this one(ar9271.fw) blew: >>> >>>http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux->>firmware.git;a=blob;f=ar9271.fw;h=0ec953b404c1912dc64fa3b0171cffae82b0f375;hb=8f919160792e4702c6b7a67a243cea4f757407e4 >>> >>>This one still can't prevent the probe failure... >> >>>Any suggestions? >> >> Could you please try it without CONFIG_USB_DEBUG option. > >I don't think disabling CONFIG_USB_DEBUG can prevent the .probe failure, >which only don't print some messages. > >So this patch does make sense, doesn't it? The recent commit "check the endpoint type against the pipe type" in usb under DEBUG is causing probe failure, It's conditional on CONFIG_USB_DEBUG, so it won't affect normal users. But this probe failure under DEBUG needs to be addressed without causing any IOT issue. Thanks, Rajkumar-- 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