From: Michael Buesch <mb@bu3sch.de>
To: "Ray Lee" <ray-lk@madrabbit.org>
Cc: bcm43xx-dev@lists.berlios.de,
"Daniel Walker" <dwalker@mvista.com>,
akpm@linux-foundation.org, mingo@elte.hu,
linux-kernel@vger.kernel.org, linux@bohmer.net,
jonathan@jonmasters.org, matthias.kaehlcke@gmail.com,
kjwinchester@gmail.com, mbuesch@freenet.de,
"John Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
Date: Fri, 14 Dec 2007 11:49:46 +0100 [thread overview]
Message-ID: <200712141149.46945.mb@bu3sch.de> (raw)
In-Reply-To: <2c0942db0712131712t6f30ab88g48cc1af27a7a6ce9@mail.gmail.com>
On Friday 14 December 2007 02:12:25 Ray Lee wrote:
> Digging a little farther into it, it looks like b43 is barfing partway
> through init as the firmware file it's looking for has changed names.
> Perhaps that's the issue. I'll take a longer look at this all
> tomorrow.
http://www.linuxwireless.org/en/users/Drivers/b43#firmwareinstallation
> Well, it only hit the main kernel October 10th. That means no final
> point release of the kernel.org kernel has even had it included! So
> testing-wise, you still haven't hit the hordes yet. Scheduling a
> removal of bcm43xx (as painful as that code is [*]), seems either
> premature or very optimistic. So, how about scheduling the removal
> once you get a feel for the bug reports that'll come in once 2.6.24 is
> released.
So you volunteer to maintain bcm43xx? Fine. Thanks a lot.
> [*] Yeah, even as a user the code is painful. It *still* locks my
> keyboard if I happen to disable the wireless while it's scanning. The
> sooner bcm43xx is dead, the better. But b43 is quite obviously not a
> full replacement for everyone.
I'm pretty sure it is.
Please carefully read the instructions on
http://www.linuxwireless.org/en/users/Drivers/b43
especially for firmware installation.
It will work very well.
--
Greetings Michael.
next prev parent reply other threads:[~2007-12-14 10:52 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071213003023.117964080@mvista.com>
2007-12-12 8:00 ` [PATCH 1/3] ps3: vuart: fix error path locking Daniel Walker
2007-12-13 2:00 ` Geoff Levand
2007-12-19 1:10 ` Andrew Morton
2007-12-19 1:54 ` Daniel Walker
2007-12-19 3:04 ` Geoff Levand
2007-12-20 19:32 ` Daniel Walker
2007-12-20 20:06 ` Andrew Morton
2007-12-20 20:13 ` Daniel Walker
2007-12-12 8:00 ` [PATCH 2/3] driver base: memory: semaphore to mutex Daniel Walker
2007-12-12 8:00 ` [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem " Daniel Walker
2007-12-13 0:48 ` Michael Buesch
2007-12-13 1:17 ` Ray Lee
2007-12-13 13:45 ` Michael Buesch
2007-12-14 0:05 ` Ray Lee
2007-12-14 0:43 ` Michael Buesch
2007-12-14 0:55 ` Harvey Harrison
2007-12-14 10:45 ` Michael Buesch
2007-12-14 1:12 ` Ray Lee
2007-12-14 10:49 ` Michael Buesch [this message]
2007-12-14 11:15 ` Ingo Molnar
2007-12-14 11:39 ` Michael Buesch
2007-12-14 12:16 ` Ingo Molnar
2007-12-14 12:31 ` Michael Buesch
2007-12-14 12:53 ` Ingo Molnar
2007-12-14 13:08 ` Michael Buesch
2007-12-14 16:06 ` Ray Lee
2007-12-14 16:49 ` Michael Buesch
2007-12-14 18:01 ` Ray Lee
2007-12-14 18:11 ` Ingo Molnar
2007-12-14 18:47 ` Ray Lee
2007-12-14 18:22 ` Michael Buesch
2007-12-14 18:45 ` Ray Lee
2007-12-14 19:05 ` Michael Buesch
2007-12-14 19:25 ` Ray Lee
2007-12-14 19:38 ` Michael Buesch
2007-12-14 19:55 ` Ray Lee
2007-12-14 20:13 ` Michael Buesch
2007-12-14 21:39 ` Ray Lee
2007-12-14 12:59 ` Simon Holm Thøgersen
2007-12-14 13:04 ` Michael Buesch
2007-12-15 0:51 ` Rafael J. Wysocki
2007-12-15 0:58 ` Larry Finger
2007-12-15 1:59 ` mvtodevnull
2007-12-15 2:27 ` Larry Finger
2007-12-15 4:37 ` mvtodevnull
2007-12-15 4:39 ` mvtodevnull
2007-12-15 7:18 ` Larry Finger
2007-12-15 12:38 ` mvtodevnull
2007-12-17 2:17 ` mvtodevnull
2007-12-17 6:52 ` Larry Finger
2007-12-17 7:17 ` mvtodevnull
2007-12-17 9:49 ` Michael Buesch
2007-12-17 10:15 ` mvtodevnull
2007-12-17 10:35 ` mvtodevnull
2007-12-17 22:04 ` mvtodevnull
2007-12-17 22:45 ` Michael Buesch
2007-12-17 23:12 ` mvtodevnull
2007-12-17 23:18 ` Michael Buesch
2007-12-17 23:27 ` mvtodevnull
2007-12-18 1:16 ` Larry Finger
2007-12-18 2:34 ` mvtodevnull
2007-12-19 2:12 ` mvtodevnull
2007-12-19 8:11 ` Larry Finger
[not found] ` <200712191046.54147.mb@bu3sch.de>
2007-12-19 13:48 ` Ingo Molnar
2007-12-15 10:57 ` Michael Buesch
2007-12-15 23:18 ` Rafael J. Wysocki
2007-12-15 23:27 ` Michael Buesch
2007-12-16 2:30 ` Larry Finger
2007-12-16 11:13 ` Michael Buesch
2007-12-16 13:56 ` Johannes Berg
2007-12-16 14:35 ` Rafael J. Wysocki
2007-12-16 14:18 ` Johannes Berg
2007-12-14 2:09 ` Larry Finger
2007-12-14 10:56 ` Ingo Molnar
2007-12-14 14:14 ` John W. Linville
2007-12-14 14:40 ` stefano.brivio
2007-12-14 16:27 ` Ray Lee
2007-12-14 16:45 ` Ray Lee
2007-12-14 16:59 ` Michael Buesch
2007-12-14 17:22 ` Ray Lee
2007-12-14 17:59 ` Ingo Molnar
2007-12-14 18:38 ` Michael Buesch
2007-12-15 1:25 ` Rafael J. Wysocki
2007-12-15 21:43 ` John W. Linville
2007-12-15 23:26 ` Rafael J. Wysocki
2007-12-16 3:20 ` Stefan Lippers-Hollmann
2007-12-16 9:22 ` Ingo Molnar
2007-12-16 11:23 ` Michael Buesch
2007-12-13 1:20 ` Daniel Walker
2007-12-13 10:13 ` Ingo Molnar
2007-12-13 11:11 ` Michael Buesch
2007-12-13 14:23 ` John W. Linville
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=200712141149.46945.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=dwalker@mvista.com \
--cc=jonathan@jonmasters.org \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=linville@tuxdriver.com \
--cc=matthias.kaehlcke@gmail.com \
--cc=mbuesch@freenet.de \
--cc=mingo@elte.hu \
--cc=ray-lk@madrabbit.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