From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: Using b43-fwcutter on Windows drivers
Date: Fri, 16 Jun 2017 08:21:48 +0200 [thread overview]
Message-ID: <20170616082148.72f3f344@wiggum> (raw)
In-Reply-To: <CAOcMMiexGBmnuiTPzzsux-wq8HUGejU4i=UckTapKe1YoAAsHQ@mail.gmail.com>
On Thu, 15 Jun 2017 18:21:40 -0400
Jo?o Paulo Rechi Vita <jprvita@endlessm.com> wrote:
> We've been trying to do some binary grepping for the first 4 bytes of
> the firmware files in the windows driver (grep -obUaP
> "\x75\x01\x00\x00" BCMWL664.SYS), but although there are some matching
> occurrences, after that the bytes start to differ. Any other
> suggestions on trying to match the firmware files with windows
> drivers?
Well, then you most likely have differing fw versions.
Try to find other binaries.
> On a another topic, is there a license file available somewhere for
> the wl MIPS drivers? I've downloaded the Asus/Netgear tarballs that
> they were originally extracted from, but couldn't find a license for
> the drivers there, just a general release notes file on the top dir,
> and some un-related licenses for different projects used in the
> router's rootfs image.
I don't know anything about the licensing.
--
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20170616/061c5758/attachment.sig>
next prev parent reply other threads:[~2017-06-16 6:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-07 1:02 Using b43-fwcutter on Windows drivers João Paulo Rechi Vita
2017-06-07 1:41 ` Larry Finger
2017-06-08 0:08 ` João Paulo Rechi Vita
2017-06-08 4:48 ` Larry Finger
2017-06-12 16:28 ` João Paulo Rechi Vita
2017-06-12 16:59 ` Michael Büsch
2017-06-15 22:21 ` João Paulo Rechi Vita
2017-06-16 6:21 ` Michael Büsch [this message]
2017-08-11 12:48 ` Robert McQueen
2017-08-11 18:44 ` 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=20170616082148.72f3f344@wiggum \
--to=m@bues.ch \
--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