From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Michael Buesch <mb@bu3sch.de>
Cc: bcm43xx-dev@lists.berlios.de,
"Simon Holm Thøgersen" <odie@cs.aau.dk>,
"Daniel Walker" <dwalker@mvista.com>,
akpm@linux-foundation.org, "Ray Lee" <ray-lk@madrabbit.org>,
matthias.kaehlcke@gmail.com, linux-kernel@vger.kernel.org,
linux@bohmer.net, kjwinchester@gmail.com,
jonathan@jonmasters.org, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
Date: Sun, 16 Dec 2007 00:18:43 +0100 [thread overview]
Message-ID: <200712160018.45613.rjw@sisk.pl> (raw)
In-Reply-To: <200712151157.44278.mb@bu3sch.de>
On Saturday, 15 of December 2007, Michael Buesch wrote:
> On Saturday 15 December 2007 01:51:47 Rafael J. Wysocki wrote:
> > On Friday, 14 of December 2007, Michael Buesch wrote:
> > > On Friday 14 December 2007 13:59:54 Simon Holm Thøgersen wrote:
> > > > > This user did get the following messages in dmesg:
> > > > >
> > > > > b43err(dev->wl, "Firmware file \"%s\" not found "
> > > > > "or load failed.\n", path);
> > > >
> > > > So the question seems to be why b43 needs version 4, when b43legacy and
> > > > bcm43x uses version 3?
> > >
> > > That's really a question, right?
> > >
> > > Well. linux-2.4 doesn't work with the linux-2.6 modutils.
> > > Windows Vista doesn't work with Windows 98 device drivers.
> > > That leads to this assumption:
> > > b43 doesn't work with version 3 firmware but needs version 4.
> > >
> > > Newer drivers supporting newer hardware need newer firmware.
> >
> > Actually, can you explain why, from the technical point of view, the version 4
> > firware is better than version 3, please?
>
> version 4 is the new firmware released by broadcom. They obviously won't
> support and write any version 3 firmware anymore. So we are forced to
> switch to version 4 firmware to support the newest hardware (like N-PHY
> in the future). It's really as simple as that.
I see, thanks.
> The difference between v3 and v4 is basically the driver API. It changed
> a lot and it is nontrivial to support both v3 and v4 in one driver.
> So we decided to stay with v3 for legacy devices and take v4 for any newer
> devices.
This is reasonable, yes.
> We have to live with that crap until someone comes up with an opensource
> firmware. :)
Well, the only problem with that is I suspect there are some "newer" cards that
work better with v3 firmware, although they are supposed to support both.
Greetings,
Rafael
next prev parent reply other threads:[~2007-12-15 22:59 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
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 [this message]
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=200712160018.45613.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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=matthias.kaehlcke@gmail.com \
--cc=mb@bu3sch.de \
--cc=mingo@elte.hu \
--cc=odie@cs.aau.dk \
--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