From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
John W Linville <linville@tuxdriver.com>,
bbullins@triad.rr.com, bcm43xx-dev@lists.berlios.de,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Fix Bluetooth coexistence SPROM coding error for Motorola 7010 variant of BCM4306
Date: Sat, 20 Sep 2008 22:51:35 +0200 [thread overview]
Message-ID: <1221943895.3023.1.camel@johannes.berg> (raw)
In-Reply-To: <200809201744.55571.mb@bu3sch.de> (sfid-20080920_174550_869772_E28C99C2)
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
On Sat, 2008-09-20 at 17:44 +0200, Michael Buesch wrote:
> On Friday 19 September 2008 21:47:38 Larry Finger wrote:
> > An additional BCM4306 has been found with the Bluetooth coexistence
> > SPROM coding error.
Does anyone actually make laptops that use these bluetooth coexistence
pins? All CSR bluetooth chips do it automatically I'm told, maybe we
should just kill them completely.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-09-20 20:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-19 19:47 [PATCH] b43: Fix Bluetooth coexistence SPROM coding error for Motorola 7010 variant of BCM4306 Larry Finger
2008-09-20 15:44 ` Michael Buesch
2008-09-20 20:51 ` Johannes Berg [this message]
2008-09-20 20:59 ` Luis R. Rodriguez
2008-09-20 21:02 ` Johannes Berg
2008-09-20 21:05 ` Luis R. Rodriguez
2008-09-20 21:11 ` Johannes Berg
2008-09-21 0:19 ` Dan Williams
2008-09-21 13:07 ` Michael Buesch
2008-09-20 21:08 ` Larry Finger
2008-09-20 21:13 ` Johannes Berg
2008-09-20 21:53 ` Larry Finger
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=1221943895.3023.1.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=bbullins@triad.rr.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).