All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Cushman <rcushman_linux@roadrunner.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: BCM4306 Questions
Date: Wed, 12 Dec 2007 19:46:58 -0500	[thread overview]
Message-ID: <47608102.5010105@roadrunner.com> (raw)
In-Reply-To: <200712121300.59811.mb@bu3sch.de>

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.

Then all I had to do was try every combination of settings in the 
"Connect to Wireless Network" dialog.  Once I clicked the "show 
credentials" box, I was up and running.

Now I realize that my offer to add the signature for the latest driver 
for my adapter to bcm43xx-fwcutter would be pointless, as bcm43xx 
apparently does not support v4.x firmware.

Perhaps when I have some free time I can build the b43 driver and give 
it a test drive. 

Thanks again.


  reply	other threads:[~2007-12-13  0:47 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 [this message]
2007-12-13  1:17         ` Pavel Roskin
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=47608102.5010105@roadrunner.com \
    --to=rcushman_linux@roadrunner.com \
    --cc=linux-wireless@vger.kernel.org \
    --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 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.