From: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
Brett Rudley <brudley@broadcom.com>,
Arend van Spriel <arend@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Kan Yan <kanyan@broadcom.com>,
wireless <linux-wireless@vger.kernel.org>,
brcm80211-dev-list@broadcom.com
Subject: Re: Question about BCM43228 and outdated description in MAINTAINERS
Date: Mon, 25 Jun 2012 22:03:55 +0200 [thread overview]
Message-ID: <1340654635.3413.19.camel@gnutoo-hplaptop> (raw)
In-Reply-To: <4FE88E1A.9050202@hauke-m.de>
On Mon, 2012-06-25 at 18:13 +0200, Hauke Mehrtens wrote:
> Add support for more chips, including (near term) BCM43227, BCM43228,
> and BCM4331. Support for additional new chips to follow.
What about the BCM43231?
There was some plans about it:
http://lists.infradead.org/pipermail/b43-dev/2012-January/002297.html
But the thread ends and then it seem that nothing was achieved.
I've a BCM43231:
Bus 001 Device 008: ID 0846:9020 NetGear, Inc. WNA3100(v1) Wireless-N
300 [Broadcom BCM43231]
Are there some wireless kernels developers in Italy or in France that
would accept a bcm43231 card in exchange of working on a driver?
Denis.
next prev parent reply other threads:[~2012-06-25 20:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-25 15:41 Question about BCM43228 and outdated description in MAINTAINERS Larry Finger
2012-06-25 16:13 ` Hauke Mehrtens
2012-06-25 20:03 ` Denis 'GNUtoo' Carikli [this message]
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=1340654635.3413.19.camel@gnutoo-hplaptop \
--to=gnutoo@no-log.org \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=hauke@hauke-m.de \
--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).