From: Michael Buesch <mb@bu3sch.de>
To: "Mike Cui" <cuicui@gmail.com>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
"Nadav Kavalerchik" <nadavkav@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: BMC4310 support (03f0:171d)
Date: Sat, 13 Sep 2008 22:03:23 +0200 [thread overview]
Message-ID: <200809132203.24007.mb@bu3sch.de> (raw)
In-Reply-To: <7c8826910809122011i23587a6bta838f2e0a7c39744@mail.gmail.com>
On Saturday 13 September 2008 05:11:50 Mike Cui wrote:
> > It is not a "BCM4315", it is a BCM4310. There is no such thing as a
> > BCM4315. Chip ID != PCI ID!
> > Most chip IDs match with their respective PCI IDs, but here are some exceptions:
> > 0x4320 is BCM4306.
> > 0x4315 is BCM4310.
> > 0x4328 is BCM4321.
> > 0x432b is BCM4322.
>
> Maybe...
>
> But on the miniPCIe chip itself, there is a sticker that says Broadcom
> 4312. But it's not a BCM4312 either, because BCM4312 actually works...
the numbers printed on the chip package are package IDs. These are
different from chip-ids sometimes. ;)
The only way to find out the chipid really is to load b43 and look
for the message saying "found Broadcom XXXX WLAN".
But still, having a chip with the same chipid and/or package ids doesn't
mean it's the same chip. :)
--
Greetings Michael.
prev parent reply other threads:[~2008-09-13 20:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4219988b0809011331j4acb1582u3239218c6b7ff573@mail.gmail.com>
2008-09-01 20:49 ` BMC4310 support (03f0:171d) Nadav Kavalerchik
2008-09-01 21:33 ` Michael Buesch
[not found] ` <4219988b0809091240s970c580k763054a56ef740b3@mail.gmail.com>
2008-09-09 19:41 ` Nadav Kavalerchik
2008-09-09 22:22 ` Larry Finger
2008-09-12 1:03 ` Pavel Roskin
2008-09-12 8:33 ` Mike Cui
2008-09-12 18:57 ` Stefanik Gábor
2008-09-13 3:11 ` Mike Cui
2008-09-13 13:04 ` Stefanik Gábor
2008-09-13 20:03 ` 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=200809132203.24007.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=cuicui@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nadavkav@gmail.com \
--cc=netrolller.3d@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 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.