From: Randy Cushman <rcushman_linux@roadrunner.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4306 Questions
Date: Thu, 13 Dec 2007 20:43:05 -0500 [thread overview]
Message-ID: <4761DFA9.3020305@roadrunner.com> (raw)
In-Reply-To: <1197508664.13188.27.camel@dv>
Pavel Roskin wrote:
> Hello!
>
>
>> 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:
>
>
Considered by itself the web page makes sense.
However considering how I process information, along with additional
factors, the process caused difficulty for me:
1) The bcm43xx-fwcutter man page and its -l option contradict the web
page, indicating that firmware can be extracted from recent versions of
bcmwl5.sys (include many versions 4.x) for use with bcm43xx.
2) Personal experience: The driver Windows XP found for this HP adapter
was unstable. This led me to treat as suspect any driver not obtained
from HP.
3) I had no way of knowing that firmware from any random driver would
work with my adapter.
4) I preferred using a driver/firmware from a trusted website over one
from an unknown website.
The above information led me to believe that I already had an
appropriate driver, so when reading the web page I repeatedly skipped
over the section discussing driver downloads.
I don't think any changes to the web page are needed. At the first sign
of trouble I should have read the instructions more carefully and
considered the possibility that there was a reason I was being
instructed to download a particular driver.
next prev parent reply other threads:[~2007-12-14 1:43 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
2007-12-14 1:43 ` Randy Cushman [this message]
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=4761DFA9.3020305@roadrunner.com \
--to=rcushman_linux@roadrunner.com \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.