From: Larry Finger <Larry.Finger@lwfinger.net>
To: Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: ALERT: firmware change for b43
Date: Sun, 19 Aug 2007 14:37:21 -0500 [thread overview]
Message-ID: <46C89BF1.5060306@lwfinger.net> (raw)
Just in case you missed the details, the latest set of changes to b43 queued by Michael will require
a new version of fwcutter, now called b43-fwcutter, and a new extraction of your firmware.
There are several changes. Most notably, the firmware for b43 and b43legacy will reside in separate
directories under /lib/firmware, or whatever is appropriate for your distro. With the new directory
structure, there will be no name clashes for firmware for b43, b43legacy, and bcm43xx. The fwpostfix
option still exists, but it is no longer essential for operation. The firmware files have also been
renamed to reflect their usage. This is most obvious for the "initvals" files. A third change
restructures the firmware files to reduce their size.
It is recommended that you update fwcutter before these patches are merged. If your version of
fwcutter was obtained with subversion, a simple 'svn update' in the fwcutter directory will suffice.
If you are using a version provided by your distro, you will need to checkout the latest version
with the command 'svn checkout svn://svn.berlios.de/bcm43xx/trunk/fwcutter'. This will create the
directory fwcutter. You should 'cd fwcutter', followed by 'make'. You then use the newly made
b43-fwcutter to extract V4 firmware. If you have BCM4301 or BCM4306/2 devices, you should also use
b43-cutter to extract V3 firmware for b43legacy. The patch to include that driver in wireless-dev
will be submitted very soon.
Larry
next reply other threads:[~2007-08-19 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 19:37 Larry Finger [this message]
2007-08-22 14:52 ` ALERT: firmware change for b43 John W. Linville
2007-08-22 15:25 ` Larry Finger
2007-08-22 17:18 ` John W. Linville
2007-08-22 18:08 ` Larry Finger
2007-08-22 18:10 ` John H.
2007-08-22 18:20 ` Larry Finger
2007-08-22 22:28 ` Michael Buesch
2007-08-23 9:12 ` David Woodhouse
2007-08-23 20:57 ` Michael Buesch
2007-08-23 22:16 ` 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=46C89BF1.5060306@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--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).