From: Faissal Bensefia <faissaloo@me.com>
To: b43-dev@lists.infradead.org
Subject: BCM43224
Date: Tue, 29 Nov 2016 10:48:36 +0000 [thread overview]
Message-ID: <7b40931a-1d1a-9baf-28d3-59568a346800@me.com> (raw)
In-Reply-To: <CACna6rzE2R2jQtViNrqvLriybxnWK1k+hw-FjSgg9Ch7ZD6jZw@mail.gmail.com>
On 28/11/16 21:03, Rafa? Mi?ecki wrote:
> On 23 November 2016 at 21:27, Faissal Bensefia <faissaloo@me.com> wrote:
>> To my knowledge the only drivers for this card are brcmsmac and
>> broadcom-wl, both of which require proprietary firmware, which I'd like
>> to do without. How can I assist in reverse engineering the BCM43224
>> firmware? Are there any resources that explain how to use b43-tools?
>
> b43 also has (very) limited support for BCM43224, after all you
> e-mailed b43 mailing list.
>
I've attempted to use b43 but on my card but it doesn't work, the module
never loads, despite me removing brcmsmac making sure that everything
has been unloaded and then loading b43, as well as blacklisting
brcmsmac, none of which worked. From what I've read there is meant to be
support but it's not been tested (I don't remember where the site was
but it had a list of Broadcom cards and their support status).
> For open firmware implementation my best suggestion is to contact
> OpenFWWF team http://netweb.ing.unibs.it/~openfwwf/
>
Thanks very much, I'll look into this.
next prev parent reply other threads:[~2016-11-29 10:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 20:27 BCM43224 Faissal Bensefia
2016-11-28 21:03 ` BCM43224 Rafał Miłecki
2016-11-29 10:48 ` Faissal Bensefia [this message]
2016-11-29 11:01 ` BCM43224 Rafał Miłecki
2016-11-29 15:01 ` BCM43224 Dora Smith
[not found] <u1d4h6rs6i83hi154hnklibm.1480451893397@email.android.com>
2016-12-03 10:31 ` BCM43224 Faissal Bensefia
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=7b40931a-1d1a-9baf-28d3-59568a346800@me.com \
--to=faissaloo@me.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