> What happens is that a special device attached via a USB HUB is not
> detected anymore, specifically usb.c claims that it cannot set the new
> The strange thing is:
> - It worked with that device (Brainboxes Bluetooth USB dongle) with
> earlier kernels.
Is this a buspowered device and if so, how much power does this drain from
the USB? I'm asking because I've just solved (kind of) a similar issue
with a 400mA device when I introduced the missing
connect-detect-to-port-reset debounce delay.
> The error messages also show a strange behaviour of the Linux USB system:
> Why does hub.c set the address and then usb.c tries the same again?
hub.c selects the address and calls usb_new_device from usb.c, which sets
(applies) the new address.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/