From: Vince Radice <vhradice@cfl.rr.com>
To: b43-dev@lists.infradead.org
Subject: Wireless Problem
Date: Thu, 09 Feb 2012 15:55:58 -0500 [thread overview]
Message-ID: <4F3432DE.9050105@cfl.rr.com> (raw)
In-Reply-To: <4F34209E.5090704@broadcom.com>
Thank you for the quick response. Some of the posts that I looked at
indicated success with what was available, but they never came back with
the proper list of what worked.
As for my question about b43-fwcutter, do I do something with this
or is it done behind the scenes by a driver?
Also, some have had success with the STA drivers. I believe that I
have installed them with yum. How can I tell if they are being used?
Can I somehow tie those drivers with my usb adapter?
Again, thanks,
Vince Radice
On 02/09/2012 02:38 PM, Arend van Spriel wrote:
> On 02/09/2012 08:17 PM, Rafa? Mi?ecki wrote:
>> 2012/2/9 Vince Radice<vhradice@cfl.rr.com>:
>>> I am having a problem trying to get a Netgear WNA3100 adapter working. I
>>> have probably been through 100+ posts and threads trying to figure out what
>>> is happening. I have attached two files. One contains the output from
>>> dmesg. The other has the output from several commands as requested in the
>>> doc.
>> This is BCM43231, fullmac device, nothing to-be-covered by b43 driver.
>> The driver that may support this chipset is brcmfmac, but for now only
>> support for BCM4329, BCM4330 and BCM43236 was recently-added. I think
>> I remember Arend saying they are not working on support for BCM43231
>> for now. I may be wrong however.
> You are correct.
>
>> We could try hacking support for this chipset by just extracting
>> firmware for BCM43231 and adding proper USB ID in brcmfmac. I don't
>> think anyone is working on this.
>>
> I believe the API between driver and firmware is different so expect
> problems doing that. I can inform just how different.
>
> Gr. AvS
>
>
next prev parent reply other threads:[~2012-02-09 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 19:00 Wireless Problem Vince Radice
2012-02-09 19:17 ` Rafał Miłecki
2012-02-09 19:38 ` Arend van Spriel
2012-02-09 20:55 ` Vince Radice [this message]
2012-02-10 6:13 ` Rafał Miłecki
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=4F3432DE.9050105@cfl.rr.com \
--to=vhradice@cfl.rr.com \
--cc=b43-dev@lists.infradead.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