From: Michael Buesch <mb@bu3sch.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Enable Bluetooth Coexistence support
Date: Fri, 2 Jan 2009 20:31:24 +0100 [thread overview]
Message-ID: <200901022031.24460.mb@bu3sch.de> (raw)
In-Reply-To: <da94abde0901021106l721ad722w9eb857ed41214377@mail.gmail.com>
On Friday 02 January 2009 20:06:08 Kalle Valo wrote:
> On Fri, Jan 2, 2009 at 8:52 PM, Stefanik G?bor <netrolller.3d@gmail.com> wrote:
> > Probably a NOBTCOEX modparam might be a good idea - when implementing
> > BT coexistence in b43, a lot of non-BT-aware cards failed to work
> > because the BT GPIO line was connected to the TX preamplifier,
> > breaking all TX.
>
> It would be nice to have a common interface for this, for example
> through nl80211. Lots of drivers have BT coexistence support. But this
> is just an idea.
Well, why? If btcoex works correctly (= is not buggy), the user does not
notice it at all. I see no reason to turn it off. Except if it's buggy.
But then we should simply fix it or always disable it at compiletime, if
it's not possible to fix.
--
Greetings, Michael.
WARNING: multiple messages have this Message-ID (diff)
From: Michael Buesch <mb@bu3sch.de>
To: "Kalle Valo" <kalle.valo@iki.fi>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
"Vasanthakumar Thiagarajan" <vasanth@atheros.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Luis.Rodriguez@atheros.com, Jouni.Malinen@atheros.com,
ath9k-devel@lists.ath9k.org
Subject: Re: [PATCH] ath9k: Enable Bluetooth Coexistence support
Date: Fri, 2 Jan 2009 20:31:24 +0100 [thread overview]
Message-ID: <200901022031.24460.mb@bu3sch.de> (raw)
In-Reply-To: <da94abde0901021106l721ad722w9eb857ed41214377@mail.gmail.com>
On Friday 02 January 2009 20:06:08 Kalle Valo wrote:
> On Fri, Jan 2, 2009 at 8:52 PM, Stefanik G=E1bor <netrolller.3d@gmail=
=2Ecom> wrote:
> > Probably a NOBTCOEX modparam might be a good idea - when implementi=
ng
> > BT coexistence in b43, a lot of non-BT-aware cards failed to work
> > because the BT GPIO line was connected to the TX preamplifier,
> > breaking all TX.
>=20
> It would be nice to have a common interface for this, for example
> through nl80211. Lots of drivers have BT coexistence support. But thi=
s
> is just an idea.
Well, why? If btcoex works correctly (=3D is not buggy), the user does =
not
notice it at all. I see no reason to turn it off. Except if it's buggy.
But then we should simply fix it or always disable it at compiletime, i=
f
it's not possible to fix.
--=20
Greetings, Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-01-02 19:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 10:05 [ath9k-devel] [PATCH] ath9k: Enable Bluetooth Coexistence support Vasanthakumar Thiagarajan
2009-01-02 10:05 ` Vasanthakumar Thiagarajan
2009-01-02 18:52 ` [ath9k-devel] " Stefanik Gábor
2009-01-02 18:52 ` Stefanik Gábor
2009-01-02 18:56 ` [ath9k-devel] " Michael Buesch
2009-01-02 18:56 ` Michael Buesch
2009-01-02 18:59 ` [ath9k-devel] " Stefanik Gábor
2009-01-02 18:59 ` Stefanik Gábor
2009-01-02 19:28 ` [ath9k-devel] " Michael Buesch
2009-01-02 19:28 ` Michael Buesch
2009-01-02 19:06 ` [ath9k-devel] " Kalle Valo
2009-01-02 19:06 ` Kalle Valo
2009-01-02 19:31 ` Michael Buesch [this message]
2009-01-02 19:31 ` Michael Buesch
2009-01-02 20:03 ` [ath9k-devel] " Kalle Valo
2009-01-02 20:03 ` Kalle Valo
2009-01-03 8:46 ` [ath9k-devel] " Vasanthakumar Thiagarajan
2009-01-03 8:46 ` Vasanthakumar Thiagarajan
2009-01-03 20:41 ` [ath9k-devel] " Stefanik Gábor
2009-01-03 20:41 ` Stefanik Gábor
2009-01-05 5:27 ` [ath9k-devel] " Vasanthakumar Thiagarajan
2009-01-05 5:27 ` Vasanthakumar Thiagarajan
2009-01-05 17:06 ` [ath9k-devel] " Luis R. Rodriguez
2009-01-05 17:06 ` Luis R. Rodriguez
2009-01-09 8:06 ` [ath9k-devel] " Vasanthakumar Thiagarajan
2009-01-09 8:06 ` Vasanthakumar Thiagarajan
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=200901022031.24460.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.