From: Stefano Brivio <stefano.brivio@polimi.it>
To: Pavel Roskin <proski@gnu.org>
Cc: Michael Buesch <mb@bu3sch.de>,
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 20:15:38 +0100 [thread overview]
Message-ID: <20080115201538.5e4347f9@morte> (raw)
In-Reply-To: <1200421662.17542.32.camel@dv>
On Tue, 15 Jan 2008 13:27:42 -0500
Pavel Roskin <proski@gnu.org> wrote:
> 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?
Good luck. ;) The only long-term lasting solution I see is to put more
effort on an open firmware. The instruction set has been figured out, we
just lack people and time there.
> 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.
fwcutter development now happens here:
http://bu3sch.de/gitweb?p=b43-tools.git;a=summary
Maybe we should add this along with git URLs on linuxwireless.org.
--
Ciao
Stefano
next prev parent reply other threads:[~2008-01-15 19:22 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
2008-01-15 19:15 ` Stefano Brivio [this message]
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=20080115201538.5e4347f9@morte \
--to=stefano.brivio@polimi.it \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=proski@gnu.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