linux-kernel - RE: Linux Bluetooth Coexistence documentation in general and for ath9k

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <35B17FE5076C7040809188FBE7913F983A1CC44471@SC1EXMB-MBCL.global.atheros.com>
Date:	Wed, 10 Mar 2010 14:11:10 -0800
From:	Mike Tsai <Mike.Tsai@...eros.com>
To:	Pavel Machek <pavel@....cz>, Marcel Holtmann <marcel@...tmann.org>
CC:	"Luis R. Rodriguez" <mcgrof@...il.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	linux-bluetooth <linux-bluetooth@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dan Tian <Dan.Tian@...eros.com>
Subject: RE: Linux Bluetooth Coexistence documentation in general and for
	ath9k

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@...r.kernel.org [mailto:linux-bluetooth-owner@...r.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@...r.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/