linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <larry.finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: ALERT: firmware change for b43
Date: Wed, 22 Aug 2007 13:08:09 -0500	[thread overview]
Message-ID: <46CC7B89.7090906@lwfinger.net> (raw)
In-Reply-To: <20070822171805.GD2926@tuxdriver.com>

John W. Linville wrote:
> On Wed, Aug 22, 2007 at 10:25:28AM -0500, Larry Finger wrote:
>> John W. Linville wrote:
>>> On Sun, Aug 19, 2007 at 02:37:21PM -0500, Larry Finger wrote:
>>>> 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.
>>> Is there a tarball available for download, as with bcm43xx-fwcutter?
>>> It would be handy for packaging.
>> The new code is in the svn repository; however, a tarball would not be a 
>> problem. Is source sufficient, or would you want an executable?
> 
> Source would be fine, equivalent to what is here:
> 
> 	http://download.berlios.de/bcm43xx/bcm43xx-fwcutter-006.tar.bz2

I don't have nor want write access at berlios.de.  The file you want is:

ftp://lwfinger.dynalias.org/patches/b43-fwcutter-008.tar.bz2.

Larry

  reply	other threads:[~2007-08-22 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-19 19:37 ALERT: firmware change for b43 Larry Finger
2007-08-22 14:52 ` 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 [this message]
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=46CC7B89.7090906@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).