linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Trouble with bcm4312 rev 01 on the HP 2133
Date: Sat, 8 Nov 2008 13:45:04 +0100	[thread overview]
Message-ID: <200811081345.04823.mb@bu3sch.de> (raw)
In-Reply-To: <200811081333.55833.mb@bu3sch.de>

On Saturday 08 November 2008 13:33:55 Michael Buesch wrote:
> On Saturday 08 November 2008 06:11:38 Ben Greear wrote:
> > lspci -x
> > 02:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g (rev 01)
> > 00: e4 14 15 43 06 01 10 00 01 00 80 02 08 00 00 00
> 
> Try this, please.
> 
> Index: wireless-testing/drivers/ssb/b43_pci_bridge.c
> ===================================================================
> --- wireless-testing.orig/drivers/ssb/b43_pci_bridge.c	2008-05-16 00:25:42.000000000 +0200
> +++ wireless-testing/drivers/ssb/b43_pci_bridge.c	2008-11-08 13:33:06.000000000 +0100
> @@ -21,6 +21,7 @@ static const struct pci_device_id b43_pc
>  	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4307) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4311) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4312) },
> +	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4315) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4318) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4319) },
>  	{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4320) },
> 

Note that your device most likely is an LP-PHY based device, which is
not supported at all. But you will notice that. It will complain about
about unsupported PHY after you applied that patch.

-- 
Greetings Michael.

      reply	other threads:[~2008-11-08 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-08  5:11 Trouble with bcm4312 rev 01 on the HP 2133 Ben Greear
2008-11-08 12:33 ` Michael Buesch
2008-11-08 12:45   ` 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=200811081345.04823.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).