Hi! > > The question of Bluetooth coexistence pops up here, on IRC and on bug > > reports quite too often so I've stuffed what I could onto a page with > > a few references / code and about ath9k's schemes for BT coexistence, > > feel free to extend or correct: > > > > http://wireless.kernel.org/en/users/Documentation/Bluetooth-coexistence > > http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex > > > > I'm still not sure if "2-wire" and "3-wire" are generic terms and if > > someone owns a trademark on them or what, but looking down the road I > > think it would be nice to export this information through nl80211, if > > a device supports any of these BT-coex schemes and if so, perhaps > > display the current signal status of: > > > > * WLAN_ACTIVE > > * BT_PRIORITY > > * BT_STATE ... > the only thing the host has control over is AFH channel map, and even > modifying that is not really needed. The Bluetooth controller will do > AFH automatically and it is on by default. We never switch that off > actually. > > Normally the co-ex stuff is hard-wired between the Bluetooth and WiFi > and thus out of control to the host OS. I believe that 'internal wifi, usb bluetooth' is still quite common setup... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
