From: "Michael Büsch" <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Odd behavior of ssb, b43, b43legacy, and b44
Date: Fri, 07 Jan 2011 15:45:55 +0100 [thread overview]
Message-ID: <1294411555.18385.1.camel@maggie> (raw)
In-Reply-To: <4D269711.1040003@lwfinger.net> (sfid-20110107_053108_647486_0233929A)
On Thu, 2011-01-06 at 22:31 -0600, Larry Finger wrote:
> On 01/06/2011 09:34 PM, Michael B?sch wrote:
> >
> > Does one of these wireless cards have a dangling ethernet core? I would
> > not be surprised...
>
> Yes. The core scan for the BCM4303 is as follows:
>
> ssb: Core 0 found: IEEE 802.11 (cc 0x812, rev 0x02, vendor 0x4243)
> ssb: Core 1 found: PCMCIA (cc 0x80D, rev 0x00, vendor 0x4243)
> ssb: Core 2 found: Fast Ethernet (cc 0x806, rev 0x02, vendor 0x4243)
> ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
> ssb: Core 4 found: PCI (cc 0x804, rev 0x03, vendor 0x4243)
> ssb: Sonics Silicon Backplane found on PCI device 0000:01:09.0
>
> Larry
>
Can you please try this patch?
Index: linux-2.6.37/drivers/ssb/scan.c
===================================================================
--- linux-2.6.37.orig/drivers/ssb/scan.c 2011-01-07 15:35:10.518000002 +0100
+++ linux-2.6.37/drivers/ssb/scan.c 2011-01-07 15:45:54.231998930 +0100
@@ -420,6 +420,16 @@
bus->pcicore.dev = dev;
#endif /* CONFIG_SSB_DRIVER_PCICORE */
break;
+ case SSB_DEV_ETHERNET:
+ if (bus->bustype == SSB_BUSTYPE_PCI) {
+ if (bus->host_pci->vendor == PCI_VENDOR_ID_BROADCOM &&
+ (bus->host_pci->device & 0xFF00) == 0x4300) {
+ /* This is a dangling ethernet core on a
+ * wireless device. Ignore it. */
+ continue;
+ }
+ }
+ break;
default:
break;
}
--
Greetings Michael.
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Odd behavior of ssb, b43, b43legacy, and b44
Date: Fri, 07 Jan 2011 15:45:55 +0100 [thread overview]
Message-ID: <1294411555.18385.1.camel@maggie> (raw)
In-Reply-To: <4D269711.1040003@lwfinger.net> (sfid-20110107_053108_647486_0233929A)
On Thu, 2011-01-06 at 22:31 -0600, Larry Finger wrote:
> On 01/06/2011 09:34 PM, Michael Büsch wrote:
> >
> > Does one of these wireless cards have a dangling ethernet core? I would
> > not be surprised...
>
> Yes. The core scan for the BCM4303 is as follows:
>
> ssb: Core 0 found: IEEE 802.11 (cc 0x812, rev 0x02, vendor 0x4243)
> ssb: Core 1 found: PCMCIA (cc 0x80D, rev 0x00, vendor 0x4243)
> ssb: Core 2 found: Fast Ethernet (cc 0x806, rev 0x02, vendor 0x4243)
> ssb: Core 3 found: V90 (cc 0x807, rev 0x01, vendor 0x4243)
> ssb: Core 4 found: PCI (cc 0x804, rev 0x03, vendor 0x4243)
> ssb: Sonics Silicon Backplane found on PCI device 0000:01:09.0
>
> Larry
>
Can you please try this patch?
Index: linux-2.6.37/drivers/ssb/scan.c
===================================================================
--- linux-2.6.37.orig/drivers/ssb/scan.c 2011-01-07 15:35:10.518000002 +0100
+++ linux-2.6.37/drivers/ssb/scan.c 2011-01-07 15:45:54.231998930 +0100
@@ -420,6 +420,16 @@
bus->pcicore.dev = dev;
#endif /* CONFIG_SSB_DRIVER_PCICORE */
break;
+ case SSB_DEV_ETHERNET:
+ if (bus->bustype == SSB_BUSTYPE_PCI) {
+ if (bus->host_pci->vendor == PCI_VENDOR_ID_BROADCOM &&
+ (bus->host_pci->device & 0xFF00) == 0x4300) {
+ /* This is a dangling ethernet core on a
+ * wireless device. Ignore it. */
+ continue;
+ }
+ }
+ break;
default:
break;
}
--
Greetings Michael.
next prev parent reply other threads:[~2011-01-07 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 20:07 Odd behavior of ssb, b43, b43legacy, and b44 Larry Finger
2011-01-06 20:07 ` Larry Finger
2011-01-07 3:34 ` Michael Büsch
2011-01-07 3:34 ` Michael Büsch
2011-01-07 4:31 ` Larry Finger
2011-01-07 4:31 ` Larry Finger
2011-01-07 14:45 ` Michael Büsch [this message]
2011-01-07 14:45 ` Michael Büsch
2011-01-07 18:03 ` Larry Finger
2011-01-07 18:03 ` 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=1294411555.18385.1.camel@maggie \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--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 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.