All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>,
	John W Linville <linville@tuxdriver.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 16:08:41 -0500	[thread overview]
Message-ID: <48D56659.5060209@lwfinger.net> (raw)
In-Reply-To: <1221943895.3023.1.camel@johannes.berg>

Johannes Berg wrote:
> 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.

I don't know, but I really wouldn't want to blindly kill bluetooth
coexistence. After all, most cards have their SPROMs programmed
correctly. Only the PCI-versions of the BCM4306 and the ASUS BCM4318
seem to have the problem.

I have been working the openSUSE and Ubuntu support forums, which is
where I have been getting these new devices to add to the work-around.

Larry


  parent reply	other threads:[~2008-09-20 21:09 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
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 [this message]
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=48D56659.5060209@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --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 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.