From: Larry Finger <Larry.Finger@lwfinger.net>
To: Brett Rudley <brudley@broadcom.com>,
Arend van Spriel <arend@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Kan Yan <kanyan@broadcom.com>
Cc: wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com
Subject: Question about BCM43228 and outdated description in MAINTAINERS
Date: Mon, 25 Jun 2012 10:41:39 -0500 [thread overview]
Message-ID: <4FE886B3.7020202@lwfinger.net> (raw)
Hi,
I recently received a donated BCM43228 (14e4:4359) mini-PCIe card. At the
moment, neither b43 nor brcmsmac support it. Although, grepping the proprietary
driver wl shows that it would recognize that PCI ID, that driver does not load
as it requires routine lockdep_init_map(), which is exported only for GPL
modules. As a result, owners of this device can only use it with Linux if they
can find a suitable Windows driver for use with ndiswrapper. In my experience,
that means that 64-bit users are out of luck.
Reverse engineering this device to be able to drive it with b43 would involve a
lot of effort. If your group is planning on adding it to brcmsmac, then I would
not undertake this project. To the fullest extent that you can, please advise me
regarding this matter.
When getting your addresses from file MAINTAINERS, I noticed that it was not
updated for the name change from brcm80211 to brcmsmac. The current info is as
follows:
BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER
M:
M: Roland Vossen <rvossen@broadcom.com>
M: Arend van Spriel <arend@broadcom.com>
M: Franky (Zhenhui) Lin <frankyl@broadcom.com>
M: Kan Yan <kanyan@broadcom.com>
L: linux-wireless@vger.kernel.org
L: brcm80211-dev-list@broadcom.com
S: Supported
F: drivers/net/wireless/brcm80211/
Thanks,
Larry
next reply other threads:[~2012-06-25 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 15:41 Larry Finger [this message]
2012-06-25 16:13 ` Question about BCM43228 and outdated description in MAINTAINERS Hauke Mehrtens
2012-06-25 20:03 ` Denis 'GNUtoo' Carikli
2012-06-25 20:22 ` Hauke Mehrtens
2012-06-25 21:25 ` Rafał Miłecki
2012-06-25 21:36 ` Hauke Mehrtens
2012-06-27 7:49 ` Arend van Spriel
2012-06-27 8:37 ` Arend van Spriel
2012-06-27 12:18 ` Rafał Miłecki
2012-06-27 15:07 ` 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=4FE886B3.7020202@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=kanyan@broadcom.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).