* [PATCH] USB-Core, Kernel 2.6.22.2
@ 2007-08-13 16:27 Steffen Koepf
2007-08-13 17:38 ` Felipe Balbi
0 siblings, 1 reply; 2+ messages in thread
From: Steffen Koepf @ 2007-08-13 16:27 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 628 bytes --]
Hello,
there is a USB-Device Init-Problem with the Apacer AE161 USB-Cardreader,
which contains the Chip AU6375. The Cardreader init fails in about 50%
of system boots, with the following lines:
usb 1-6: unable to read config index 0 descriptor/all
usb 1-6: can't read configurations, error -71
hub 1-0:1.0: Cannot enable port 6. Maybe the USB cable is bad?
The patch let's the kernel stay in the loop, the cardreader is detected
properly and the loop is never executed more than two times. The second
call of usb_control_msg succeeds always. Maybe it was the developer's
goal of the loop to fix such things?
cu,
Steffen
[-- Attachment #2: usb-initfix.diff.gz --]
[-- Type: application/x-gunzip, Size: 234 bytes --]
[-- Attachment #3: README --]
[-- Type: text/plain, Size: 72 bytes --]
USB-Cardreader (AU6375) init fix, Steffen Koepf, steffen.koepf@opaya.de
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH] USB-Core, Kernel 2.6.22.2
2007-08-13 16:27 [PATCH] USB-Core, Kernel 2.6.22.2 Steffen Koepf
@ 2007-08-13 17:38 ` Felipe Balbi
0 siblings, 0 replies; 2+ messages in thread
From: Felipe Balbi @ 2007-08-13 17:38 UTC (permalink / raw)
To: Steffen Koepf; +Cc: linux-kernel
Hi,
On 8/13/07, Steffen Koepf <steffen.koepf@opaya.de> wrote:
> Hello,
>
> there is a USB-Device Init-Problem with the Apacer AE161 USB-Cardreader,
> which contains the Chip AU6375. The Cardreader init fails in about 50%
> of system boots, with the following lines:
>
> usb 1-6: unable to read config index 0 descriptor/all
> usb 1-6: can't read configurations, error -71
> hub 1-0:1.0: Cannot enable port 6. Maybe the USB cable is bad?
>
> The patch let's the kernel stay in the loop, the cardreader is detected
> properly and the loop is never executed more than two times. The second
> call of usb_control_msg succeeds always. Maybe it was the developer's
> goal of the loop to fix such things?
Could you repost your patch following what is said in
Documentation/SubmittingPatches ??
thanks
>
> cu,
>
> Steffen
>
>
>
--
Best Regards,
Felipe Balbi
felipebalbi@users.sourceforge.net
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-08-13 17:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-13 16:27 [PATCH] USB-Core, Kernel 2.6.22.2 Steffen Koepf
2007-08-13 17:38 ` Felipe Balbi
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.