From: Pavel Roskin <proski@gnu.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: John Linville <linville@tuxdriver.com>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Add support for new firmware
Date: Tue, 15 Jan 2008 13:27:42 -0500 [thread overview]
Message-ID: <1200421662.17542.32.camel@dv> (raw)
In-Reply-To: <200801131420.52995.mb@bu3sch.de>
On Sun, 2008-01-13 at 14:20 +0100, Michael Buesch wrote:
> This patch adds support for new firmware.
> Old firmware is still supported until July 2008.
>
> To get new firmware, go to
> ftp://ftp.linksys.com/opensourcecode/wrt150nv11/1.51.3/
> and download the tarball. We don't have a smaller tarball, yet.
> That will be fixed later.
I have finally found some time and hardware to test it, but the tarball
is overwhelming at its 186M. And the worst thing, the server
disconnected after 30M and appears to be down right now. P.S. It's up,
ETA is 48 minutes.
There were two files there. I hope either is fine. I'm trying to
download WRT150NV11_v1.51.3_ETSI.tgz
Cannot we petition Linksys to put wl_ap.o outside the tarball? Or maybe
Broadcom could do it?
Even a zip file would be better. It's possible to cut a part of the zip
file and uncompress it with gzip.
It's really a travesty of open source. The file is "available", but you
have do download 186M of useless (for me at least) mips compilers and
other stuff. And I have a relatively good connection.
> You can extract firmware out of the "wl_ap.o" file contained
> in this tarball using latest fwcutter. You must pass the option
> --unsupported to fwcutter.
> Fwcutter-010 with official support for a new firmware image will
> be released soon.
Do you know that the Subversion repository of fwcutter has no files at
all? I mean svn://svn.berlios.de/bcm43xx/trunk
Yes, I will try --unsupported, with version 009.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-01-15 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 13:20 [PATCH] b43: Add support for new firmware Michael Buesch
2008-01-15 18:27 ` Pavel Roskin [this message]
2008-01-15 19:15 ` Stefano Brivio
2008-01-15 22:21 ` Michael Buesch
2008-01-15 22:57 ` Michael Buesch
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=1200421662.17542.32.camel@dv \
--to=proski@gnu.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
/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).