linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	Michael Buesch <mb@bu3sch.de>,
	bbullins@triad.rr.com, linux-wireless@vger.kernel.org,
	bcm43xx-dev@lists.berlios.de,
	Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH] b43: Fix Bluetooth coexistence SPROM coding error for Motorola 7010 variant of BCM4306
Date: Sat, 20 Sep 2008 17:19:11 -0700	[thread overview]
Message-ID: <1221956351.15866.1.camel@localhost.localdomain> (raw)
In-Reply-To: <1221945075.3023.14.camel@johannes.berg>

On Sat, 2008-09-20 at 23:11 +0200, Johannes Berg wrote:
> On Sat, 2008-09-20 at 14:05 -0700, Luis R. Rodriguez wrote:
> 
> > >> > 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.
> > >>
> > >> Regardless of the wireless card? Or just for bcm?
> > >
> > > Well just for b43(legacy), but out of curiosity, does any BT chip use
> > > these pins anyway? Well I guess _somebody_ has to buy BCMs BT chips,
> > > but ...
> > 
> > BCM BT chips? I thought you said CSR?
> 
> Well the thing is, BCM wifi chips have these IO pins that tell the BT
> chip what the wifi chip is doing. But CSR chips for instance don't care,
> they just check what the wifi chip is doing on the antenna. So those
> don't use those IO pins.

Marvell SD 8686 have these pins too; I have at least one sample of such
a setup.  Not that I have had time yet to implement it...  but this sort
of thing exists of course.

Dan

> Hence, I'm wondering if there's any use in the IO pins at all. But they
> must have added them for a reason, presumably because their own BT chips
> can use those inputs...
> 
> Anyway, mostly just idly wondering, since most of the time it works fine
> and the EEPROM is actually done right I guess we should keep them on.
> 
> johannes


  reply	other threads:[~2008-09-21  0:21 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 [this message]
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=1221956351.15866.1.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=bbullins@triad.rr.com \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=mcgrof@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).