Marcel, a question for you below. 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 I do wonder if this could be useful to network applets like network manager/connman. The other BT coex schemes are BT specific it seems and not sure if those devices can expose that information out and inform userspace of certain events. Marcel, does the BlueZ support exporting if certain bt-coex schemes are supported like AFH, channel skipping, TDM, and also if they are being used and details of that? Luis -- 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
