Am Samstag, 23. Juni 2012, 10:46:12 schrieb James: > On Fri, 2012-06-22 at 08:26 +0200, Oliver Neukum wrote: > > > Basically the device is semi-reset and ath3k cannot deal with a device > > in that state. But that doesn't tell us what can be done. Please post "lsusb -v" > > of your device _before_ ath3k is loaded (you should disable ath3k and btusb > > for that test) in both states, after cold boot and warm reboot from Windows. > > I blacklisted ath3k and btusb and captured the following lsusb -v > outputs for the device, which are attached with names as follows: > > 1. lsusb-cold_linux.log > Taken from a cold boot straight into Linux. [Manually loaded ath3k > and btusb afterwards, and everything worked properly.] > > 2. lsusb-after_win7.log > Taken after warm reboot into Linux from Windows 7. Here, lsusb -v > worked without the strange delay. Hm. This is a bit problematic as we already do a reset in the enumeration process. And we cannot tell the states apart based on the descriptors. Al, any idea? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
