Return-path: Received: from mail.atheros.com ([12.36.123.2]:34542 "EHLO mail.atheros.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932813Ab0CJWMO convert rfc822-to-8bit (ORCPT ); Wed, 10 Mar 2010 17:12:14 -0500 Received: from mail.atheros.com ([10.10.20.108]) by sidewinder.atheros.com for ; Wed, 10 Mar 2010 14:12:14 -0800 From: Mike Tsai To: Pavel Machek , Marcel Holtmann CC: "Luis R. Rodriguez" , linux-wireless , linux-bluetooth , "linux-kernel@vger.kernel.org" , Dan Tian Date: Wed, 10 Mar 2010 14:11:10 -0800 Subject: RE: Linux Bluetooth Coexistence documentation in general and for ath9k Message-ID: <35B17FE5076C7040809188FBE7913F983A1CC44471@SC1EXMB-MBCL.global.atheros.com> References: <43e72e891003031643u353c72dcj23bf429363a16ec8@mail.gmail.com> <1267715451.29510.20.camel@localhost.localdomain> <20100310204818.GF1394@ucw.cz> In-Reply-To: <20100310204818.GF1394@ucw.cz> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, I think host shall provide channel map to controller because it is considered to be much more accurate than the channel map generated by controller based on the RSSI reading. Mike -----Original Message----- From: linux-bluetooth-owner@vger.kernel.org [mailto:linux-bluetooth-owner@vger.kernel.org] On Behalf Of Pavel Machek Sent: Wednesday, March 10, 2010 12:48 PM To: Marcel Holtmann Cc: Luis R. Rodriguez; linux-wireless; linux-bluetooth; linux-kernel@vger.kernel.org; Dan Tian Subject: Re: Linux Bluetooth Coexistence documentation in general and for ath9k 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-bluetooth" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html