From: Pavel Roskin <proski@gnu.org>
To: Randy Cushman <rcushman_linux@roadrunner.com>
Cc: Michael Buesch <mb@bu3sch.de>, linux-wireless@vger.kernel.org
Subject: Re: BCM4306 Questions
Date: Wed, 12 Dec 2007 20:17:44 -0500 [thread overview]
Message-ID: <1197508664.13188.27.camel@dv> (raw)
In-Reply-To: <47608102.5010105@roadrunner.com>
Hello!
On Wed, 2007-12-12 at 19:46 -0500, Randy Cushman wrote:
> Michael Buesch wrote:
> > Not at all.
> > You have to read the webpage. Here's the link again:
> > http://www.linuxwireless.org/en/users/Drivers/b43#devicefirmware
> > Everything is described there.
> >
> >
> Thank you for being patient with me.
>
> When I read that web page for the fourth time, I finally realized that
> what I needed to do was forget about using the correct driver for my
> adapter, and instead download an ancient driver for an unidentified
> adapter from a website of unknown authenticity, and use the firmware
> from that driver instead. Should have been obvious, I guess.
I have looked at that page, and I don't see anything confusing there. I
wish I could improve it, but I don't see how.
The firmware checksum is verified, so either you are getting the right
firmware, or you are not getting any.
There is no talk of choosing "the correct driver". Instead, the page
suggests downloading both firmwares rather than guessing:
"If you are unsure and don't know what we are talking about here, always
build both b43 and b43legacy (and get firmware for both too). The kernel
autoloader will automatically do the right thing and load the correct
driver for your device."
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-12-13 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 0:39 BCM4306 Questions Randy Cushman
2007-12-12 11:14 ` Michael Buesch
[not found] ` <475FCB46.2030209@roadrunner.com>
2007-12-12 12:00 ` Michael Buesch
2007-12-13 0:46 ` Randy Cushman
2007-12-13 1:17 ` Pavel Roskin [this message]
2007-12-14 1:43 ` Randy Cushman
2007-12-14 4:21 ` Pavel Roskin
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=1197508664.13188.27.camel@dv \
--to=proski@gnu.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=rcushman_linux@roadrunner.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).