From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
linux-bluetooth <linux-bluetooth@vger.kernel.org>,
linux-kernel@vger.kernel.org, "Kevin Hayes\" <kevin@atheros.com>,
\"Dan Tian\"" <Dan.Tian@atheros.com>
Subject: Re: Linux Bluetooth Coexistence documentation in general and for ath9k
Date: Wed, 3 Mar 2010 21:09:55 -0800 [thread overview]
Message-ID: <43e72e891003032109v59f1ff52odb60de6111cfec53@mail.gmail.com> (raw)
In-Reply-To: <1267664353.10407.1960.camel@localhost.localdomain>
On Wed, Mar 3, 2010 at 4:59 PM, Bastien Nocera <hadess@hadess.net> wrote:
> 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.
I wasn't really thinking of buttons for BT coex, but instead just
information exposed out and making it available. Reason for this is
users tend to be blind about btcoex stuff and it would be nice if we
had a way to inform the user of the btcoex mechanisms that actually
are being used. Does that change your answer?
Luis
next prev parent reply other threads:[~2010-03-04 5:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 0:43 Linux Bluetooth Coexistence documentation in general and for ath9k Luis R. Rodriguez
2010-03-04 0:59 ` Bastien Nocera
2010-03-04 5:09 ` Luis R. Rodriguez [this message]
2010-03-04 10:18 ` Bastien Nocera
2010-03-04 15:10 ` Marcel Holtmann
2010-03-10 20:48 ` Pavel Machek
2010-03-10 22:11 ` Mike Tsai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43e72e891003032109v59f1ff52odb60de6111cfec53@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=Dan.Tian@atheros.com \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox