Am Sonntag 14 Januar 2007 10:28 schrieb Oliver Neukum: > > Have you confirmed that by using a kernel without CONFIG_USB_SUSPEND ? BTW, these are my USB config options, which don't seem to make problems anymore as long as USB_SUSPEND isn't activated: CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y CONFIG_USB_ARCH_HAS_EHCI=y CONFIG_USB=m CONFIG_USB_DEVICEFS=y CONFIG_USB_BANDWIDTH=y CONFIG_USB_MULTITHREAD_PROBE=y CONFIG_USB_EHCI_HCD=m CONFIG_USB_EHCI_SPLIT_ISO=y CONFIG_USB_EHCI_ROOT_HUB_TT=y CONFIG_USB_EHCI_TT_NEWSCHED=y CONFIG_USB_OHCI_HCD=m CONFIG_USB_OHCI_LITTLE_ENDIAN=y CONFIG_USB_PRINTER=m CONFIG_USB_STORAGE=m -- (°= =°) //\ Prakash Punnoor /\\ V_/ \_V
Attachment:
pgpkWFXeHydCy.pgp
Description: PGP signature
- References:
- 2.6.20-rc4: usb somehow broken
- From: Prakash Punnoor <[email protected]>
- Re: 2.6.20-rc4: usb somehow broken
- From: Prakash Punnoor <[email protected]>
- Re: 2.6.20-rc4: usb somehow broken
- From: Oliver Neukum <[email protected]>
- 2.6.20-rc4: usb somehow broken
- Prev by Date: Re: 2.6.20-rc4: usb somehow broken
- Next by Date: KVM: vmwrite error in
- Previous by thread: Re: [linux-usb-devel] 2.6.20-rc4: usb somehow broken
- Next by thread: Re: 2.6.20-rc4: usb somehow broken
- Index(es):