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] [thread-next>] [day] [month] [year] [list]

Message-ID: <43e72e891003032109v59f1ff52odb60de6111cfec53@mail.gmail.com>
Date:	Wed, 3 Mar 2010 21:09:55 -0800
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	Bastien Nocera <hadess@...ess.net>
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, Mar 3, 2010 at 4:59 PM, Bastien Nocera <hadess@...ess.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
--
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/