https://bugzilla.novell.com/show_bug.cgi?id=461369 User seife@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461369#c13 Stefan Seyfried <seife@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|e.john.feig@gmail.com | --- Comment #13 from Stefan Seyfried <seife@novell.com> 2009-01-08 08:01:06 MST --- Ok. I'll explain the issue: The reset=1 flag is a workaround for some (broken? non-spec? ...) adapters. Unfortunately, you cannot use it on all adapters, since some of them (older ones, I think) will not work with it, maybe because the low-level reset command changed semantics some time ago, i don't remember exactly anymore. The old hci_usb driver had a pretty large list of quirks for different devices, for example listing all devices that need "reset=1". The new btusb driver was created, and the workaround list was missing first. This is why you need to give "reset=1" to the module. The solution for the future is, that the btusb module will use "reset=1" always, _except_ for devices that are in a "blacklist". This is done because all new devices should have no problems with "reset=1", but might have problems without. The old devices (a potentially much lower number than all the new ones) will get blacklisted and everything will be fine. Unfortunately, the driver in 11.1 does not yet have this mechanism, so this is why you need to configure this manually for now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.