From: strk <strk@keybit.net>
To: b43-dev@lists.infradead.org
Subject: BCM4303 and kill switch again
Date: Sun, 4 Apr 2010 13:34:30 +0200 [thread overview]
Message-ID: <20100404113430.GO63699@keybit.net> (raw)
Hi all,
dunno if you remember the problem I've reported long
time ago about mini BCM4303 on my Asus L5800C laptop
breaking after an upgrade. Thread starts here [1].
Well, this mail is just to let you know that the ndsiwrapper
based driver works, so we can exclude hardware failures.
I'd be much happier using the free software driver of course
so if you can suggest something else to debug, I might do that.
Just a note: in order for the ndsiwrapper to function
I had to load it manually after removing the b44,b43legacy
and finally ssb drivers. Loading the ssb driver *after*
ndiswrapper is ok, but doing before results in freezes.
[1] https://lists.berlios.de/pipermail/bcm43xx-dev/2010-February/006930.html
--strk;
() Free GIS & Flash consultant/developer
/\ http://strk.keybit.net/services.html
next reply other threads:[~2010-04-04 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 11:34 strk [this message]
2010-04-04 14:54 ` BCM4303 and kill switch again Larry Finger
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=20100404113430.GO63699@keybit.net \
--to=strk@keybit.net \
--cc=b43-dev@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).