linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Vasanth Thiagarajan <Vasanth.Thiagarajan@Atheros.com>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Luis Rodriguez" <Luis.Rodriguez@Atheros.com>,
	"Jouni Malinen" <Jouni.Malinen@Atheros.com>,
	"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>
Subject: Re: [PATCH] ath9k: Enable Bluetooth Coexistence support
Date: Mon, 5 Jan 2009 09:06:47 -0800	[thread overview]
Message-ID: <20090105170647.GB6834@tesla> (raw)
In-Reply-To: <20090105052709.GA19024@vasanth-laptop>

On Sun, Jan 04, 2009 at 09:27:09PM -0800, Vasanth Thiagarajan wrote:
> On Sun, Jan 04, 2009 at 02:11:01AM +0530, Stefanik G=E1bor wrote:
>=20
> > Broadcom's BT coex was also running correctly on Windows Vista, but=
 it
> > still caused problems on Linux.
>=20
> I dont know about Broadcom BT coex implementation and issues. As far
> as Atheros chip is cocerned the BT Coex stuff is fully taken care in
> h/w. All I can say is, this BT Coex has gone through enough
> throughput testing on BT coex aware/unaware platforms to make sure
> it does not break anything both on Linux and Windows. Lets not add
> any module parameter to enable/disable BT coex for no reason.

Broadcom also does not provide support, we do ;) Please also not this i=
s only
enabled for newer chipsets.

  Luis
--
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

  reply	other threads:[~2009-01-05 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02 10:05 [PATCH] ath9k: Enable Bluetooth Coexistence support Vasanthakumar Thiagarajan
2009-01-02 18:52 ` Stefanik Gábor
2009-01-02 18:56   ` Michael Buesch
2009-01-02 18:59     ` Stefanik Gábor
2009-01-02 19:28       ` Michael Buesch
2009-01-02 19:06   ` Kalle Valo
2009-01-02 19:31     ` Michael Buesch
2009-01-02 20:03       ` Kalle Valo
2009-01-03  8:46   ` Vasanthakumar Thiagarajan
2009-01-03 20:41     ` Stefanik Gábor
2009-01-05  5:27       ` Vasanthakumar Thiagarajan
2009-01-05 17:06         ` Luis R. Rodriguez [this message]
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=20090105170647.GB6834@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Jouni.Malinen@Atheros.com \
    --cc=Luis.Rodriguez@Atheros.com \
    --cc=Vasanth.Thiagarajan@Atheros.com \
    --cc=ath9k-devel@lists.ath9k.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netrolller.3d@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).