From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: John W Linville <linville@tuxdriver.com>,
tim.gardner@canonical.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Fix for another Bluetooth Coexistence SPROM Programming error for BCM4306
Date: Fri, 15 Aug 2008 02:06:42 +0200 [thread overview]
Message-ID: <200808150206.43088.mb@bu3sch.de> (raw)
In-Reply-To: <48a4c657.3Vw2yJT7Y4Gu6f4D%Larry.Finger@lwfinger.net>
On Friday 15 August 2008 01:57:11 Larry Finger wrote:
> In trying to help users on the Ubuntu Bugzilla, I discovered another
> BCM4306 with the Bluetooth Coexistence programming error in the SPROM.
>
> This patch is contingent on the one that added the Linksys device with
> subdevice code of 0x0014.
>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Stable <stable@kernel.org>
> ---
>
> John,
>
> This is more 2.6.27 material.
ACK
> Larry
> ---
>
> Index: wireless-testing/drivers/net/wireless/b43/main.c
> ===================================================================
> --- wireless-testing.orig/drivers/net/wireless/b43/main.c
> +++ wireless-testing/drivers/net/wireless/b43/main.c
> @@ -4615,6 +4615,7 @@ static void b43_sprom_fixup(struct ssb_b
> if (bus->bustype == SSB_BUSTYPE_PCI) {
> pdev = bus->host_pci;
> if (IS_PDEV(pdev, BROADCOM, 0x4318, ASUSTEK, 0x100F) ||
> + IS_PDEV(pdev, BROADCOM, 0x4320, DELL, 0x0003) ||
> IS_PDEV(pdev, BROADCOM, 0x4320, LINKSYS, 0x0015) ||
> IS_PDEV(pdev, BROADCOM, 0x4320, LINKSYS, 0x0014) ||
> IS_PDEV(pdev, BROADCOM, 0x4320, LINKSYS, 0x0013))
>
>
>
>
--
Greetings Michael.
prev parent reply other threads:[~2008-08-15 0:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 23:57 [PATCH] b43: Fix for another Bluetooth Coexistence SPROM Programming error for BCM4306 Larry Finger
2008-08-15 0:06 ` Michael Buesch [this message]
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=200808150206.43088.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=tim.gardner@canonical.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).