From: "Michael Büsch" <mb@bu3sch.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
b43-dev <b43-dev@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH, RFC] linux-firmware: Add assembler/disassembler toolchain for broadcom wireless firmware
Date: Tue, 21 Sep 2010 14:47:01 +0200 [thread overview]
Message-ID: <1285073221.32401.24.camel@maggie> (raw)
[-- Attachment #1: Type: text/plain, Size: 1054 bytes --]
This adds a Broadcom wireless firmware assembler/disassembler toolchain
to the linux-firmware git tree.
Supported firmware architectures include r5 (chipsets supported by b43)
and r15 (brcm80211). Support for r5 is complete. r15 support misses support for
decoding of some minor instructions. This is work in progress.
Older chipsets (b43legacy) are not supported.
The instruction set is Broadcom-proprietary. However, no information
about mnemonics was provided by Broadcom. So a new set of mnemonics was invented.
The toolchain passes a complete regression test (disassemble -> reassemble -> binary compare)
on both r5 and r15 firmware.
More information on the instruction set can be found here:
http://bcm-v4.sipsolutions.net/802.11/Microcode
(Lacks some information on new r15 features)
The toolchain is licensed under the GNU/GPL version 2.
Signed-off-by: Michael Buesch <mb@bu3sch.de>
---
A compressed patch is attached. Uncompressed patch can be obtained from here:
http://bu3sch.de/patches/misc/brcm-asm-001.patch
--
Greetings Michael.
[-- Attachment #2: brcm-asm-001.patch.bz2 --]
[-- Type: application/x-bzip, Size: 39859 bytes --]
reply other threads:[~2010-09-21 12:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1285073221.32401.24.camel@maggie \
--to=mb@bu3sch.de \
--cc=b43-dev@lists.infradead.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).