From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Questions about firmware
Date: Sun, 14 Aug 2011 12:59:55 -0500 [thread overview]
Message-ID: <4E480D1B.2000805@lwfinger.net> (raw)
Rafa?,
I have finished modifying fwcutter to handle the 5 new files in your site that
are now transferred to mine. I will be sending the patches to Michael as soon as
the issue of the location of the files is resolved.
As I understand it, one needs to extract firmware from the 5.100.138 driver to
handle an HT PHY; however, my experience is that the older FW is also converted
to the new RX descriptors, and that using it with an unmodified driver will fail.
As I am in the process of updating the install_bcm43xx_firmware script for
openSUSE, we need to decide how to handle the situation. Thus far, I have two
possible solutions:
1. Change the default firmware directory for any version of b43 that has the
newest version of the RX header. In this case, fwcutter would be modified to use
the revision level of the FW to decide the output directory. The openSUSE script
would need to download and cut FW from both 5.100.138 and 5.10.144.3. The extra
11 or 12 MB of download is a pain, but at least it is not 50-100 MB.
2. Change the openSUSE script to download and cut from 5.100.138 followed by an
immediate download and cut from 5.10.144.3 with the output from both going to
/lib/firmware/b43. Is there a clean separation between the devices that need the
new firmware so that this would work? Of course, the openSUSE script still needs
to download two drivers. I see no way around that.
I favor #1 for several reasons. It is distro agnostic. All the users need is
access to the latest version of fwcutter. In addition, I'm sure that it will
work for all versions of the driver and the hardware.
Any other ideas?
Larry
next reply other threads:[~2011-08-14 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 17:59 Larry Finger [this message]
2011-08-14 18:21 ` Questions about firmware Rafał Miłecki
2011-08-14 18:31 ` Larry Finger
2011-08-14 18:35 ` Rafał Miłecki
2011-08-14 19:03 ` Larry Finger
2011-08-14 18:48 ` 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=4E480D1B.2000805@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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