[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1267664353.10407.1960.camel@localhost.localdomain>
Date: Thu, 04 Mar 2010 00:59:13 +0000
From: Bastien Nocera <hadess@...ess.net>
To: "Luis R. Rodriguez" <mcgrof@...il.com>
Cc: linux-wireless <linux-wireless@...r.kernel.org>,
linux-bluetooth <linux-bluetooth@...r.kernel.org>,
linux-kernel@...r.kernel.org,
"Kevin Hayes\" <kevin@...eros.com>, \"Dan Tian\""
<Dan.Tian@...eros.com>
Subject: Re: Linux Bluetooth Coexistence documentation in general and for
ath9k
On Wed, 2010-03-03 at 16:43 -0800, Luis R. Rodriguez wrote:
> 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:
<snip>
> I do wonder if this could be useful to network applets like network
> manager/connman.
Not really. To me, it sounds like a "make it work" button. The kernel
bits of Bluetooth should already have an idea of when a device is
connected, so the kernel should be able to "do the right thing".
Having options over what "the right thing" is is probably a good idea
whilst the kinks are worked out from the default behaviour, but this is
not something that should be advertised to users.
> 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.
Cheers
--
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/
Powered by blists - more mailing lists