From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Michael Buesch <mb@bu3sch.de>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: bcm4301: A mac80211 driver using V3 firmware
Date: Thu, 19 Jul 2007 17:58:01 -0400 [thread overview]
Message-ID: <20070719215801.GB12449@tuxdriver.com> (raw)
In-Reply-To: <46963C0F.3080104@lwfinger.net>
On Thu, Jul 12, 2007 at 09:34:55AM -0500, Larry Finger wrote:
> My plan is to clean up the code, check it with my BCM4306 and BCM4318
> devices, and then make it available as a patch against the mainline source
> for more general testing. At the same time, I will publish the results of
> my performance testing of all 3 models. Once it is shown to be reliable, a
> decision can be made regarding its inclusion in mainline and if it should
> support B and G devices, or be restricted to B-only devices. The A-PHY code
> has been stripped out.
This sounds great. Perhaps this can be the migration vehicle for
current bcm43xx users to come to mac80211? Especially for those with
hardware not supported by the current bcm43xx-mac80211 driver.
Are you proposing to add a third driver and deprecate the softmac
driver? Or can we treat this as a port of the existing driver
to mac80211? I think that might be better for users and distros,
and might let us get rid of the softmac component that much sooner.
As for the name, if we treat this as a port of the current driver to
mac80211 then perhaps we should just continue using the "bcm43xx" name?
If so, we need a new name for the v4-based driver -- "bcm43xxtoo"? :-)
Regarding hardware support, I have begun to lean towards having
the v3 driver continue to support all the hardware it does now.
I'm certainly prepared to hear the downside of that position. :-)
What exactly do we gain from using the v4 firmware?
Anyway, I'm glad to hear we are making progress on this front.
Good job, Larry!
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-19 22:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 14:34 bcm4301: A mac80211 driver using V3 firmware Larry Finger
2007-07-19 21:58 ` John W. Linville [this message]
2007-07-19 22:26 ` Johannes Berg
2007-07-19 23:27 ` Stefano Brivio
2007-07-20 1:38 ` Larry Finger
2007-07-20 3:09 ` Stefano Brivio
2007-07-20 4:43 ` Pavel Roskin
2007-07-20 12:12 ` David Woodhouse
2007-07-20 13:44 ` John W. Linville
2007-07-20 16:05 ` Pavel Roskin
2007-07-20 16:33 ` Ehud Gavron
2007-07-20 17:57 ` Pavel Roskin
2007-07-20 18:05 ` John W. Linville
2007-07-20 20:41 ` Larry Finger
2007-07-21 12:50 ` Michael Buesch
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=20070719215801.GB12449@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--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 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).