From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
Abimanyu Gottumukkala <me@abimanyu.in>,
linux-wireless@vger.kernel.org,
Arend van Spriel <arend@broadcom.com>
Subject: Re: BCM43231
Date: Mon, 09 Jan 2012 16:18:34 -0600 [thread overview]
Message-ID: <4F0B67BA.20207@lwfinger.net> (raw)
In-Reply-To: <CACna6rzNrFWBJ+n3n9wrnP_Gi3LKCWt+o1Gs38_EjkMgG_k8vg@mail.gmail.com>
On 01/09/2012 02:12 PM, Rafał Miłecki wrote:
> 2011/12/30 Abimanyu Gottumukkala<me@abimanyu.in>:
>> Does any one have status or any info on BCM43231 USB drivers?
>
> I've received my WNA3100, 0846:9020 (maybe BCM43231, can't confirm).
>
> It works with ndiswrapper and bcmwlhigh6, I can scan and even connect
> to my WPA2 network.
>
> Unfortunately I've no idea what hardware is this. I've dumped
> ndiswrapper USB operations but they don't tell me a single thing.
> Initialization is represented by only ~1000 lines in dumps and I've
> connected in next ~1500 lines of USB dump. I've been using "usbmon" to
> dump traffic.
The evidence points to some kind of Broadcom chip. The USB data base says that
an ID of "0846:9020" is a "WNA3100(v1) Wireless-N 300 [Broadcom BCM43231]". In
addition, the Windows driver name of bcmwlhigh6 indicates a BroadCoM WL driver
of some sort. Given the relatively small amount of initialization traffic, it
must be a fullmac device that likely does not need external firmware.
I remember seeing some mail about the Broadcom guys working on a Linux driver
for a USB fullmac device. Is this the one? (I added Arend to the Cc.)
Larry
next prev parent reply other threads:[~2012-01-09 22:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 12:58 BCM43231 Abimanyu Gottumukkala
2011-12-31 16:46 ` BCM43231 Rafał Miłecki
2012-01-09 20:12 ` BCM43231 Rafał Miłecki
2012-01-09 22:18 ` Larry Finger [this message]
2012-01-10 11:07 ` BCM43231 Arend van Spriel
2012-01-10 11:14 ` BCM43231 Rafał Miłecki
2012-01-10 12:17 ` BCM43231 Arend van Spriel
2012-01-09 21:31 ` BCM43231 Rafał Miłecki
2012-01-09 22:25 ` BCM43231 Peter Stuge
2012-01-09 22:28 ` BCM43231 Rafał Miłecki
2012-01-09 23:14 ` BCM43231 Gábor Stefanik
2012-01-10 7:00 ` BCM43231 Rafał Miłecki
2012-01-10 7:29 ` BCM43231 Rafał Miłecki
2012-01-10 9:36 ` BCM43231 Michael Büsch
2012-01-10 16:59 ` BCM43231 Peter Stuge
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=4F0B67BA.20207@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@abimanyu.in \
--cc=zajec5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox