From: Stefano Brivio <stefano.brivio@polimi.it>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
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: Fri, 20 Jul 2007 01:27:14 +0200 [thread overview]
Message-ID: <20070720012714.0dc0298a@morte> (raw)
In-Reply-To: <20070719215801.GB12449@tuxdriver.com>
On Thu, 19 Jul 2007 17:58:01 -0400
"John W. Linville" <linville@tuxdriver.com> wrote:
> 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.
I agree. Let's treat this as a port, as soon as it's stable. By the way, I
hope I'll be able to contribute again starting on July, 25.
> 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"? :-)
Should the ported driver support 802.11g devices as well, it should be
called bcm43xx, IMHO. Else, IIRC, we already discussed that and it should
be called bcm4301. bcm43xx-mac80211 could be renamed to "bcm43xx-v4", it
would be more meaningful than "bcm43xtoo", maybe.
> Regarding hardware support, I have begun to lean towards having
> the v3 driver continue to support all the hardware it does now.
I agree. But I would wait a little more time, I mean, when the ported driver
is stable, then let's consider the status of "bcm43xx-v4". Michael is
actually making some progress, even if - sadly - he's alone right now.
The final plan should be something like this:
1) bcm43xx gets stable and merged;
2) bcm43xx-mac80211 is renamed to bcm43xx-v4 and doesn't get merged;
3) when bcm43xx-v4 gets stable, the PCI IDs list of bcm43xx gets stripped
down and it is renamed to bcm4301, while bcm43xx-v4 is renamed to bcm43xx.
This could lead to some troubles. The other possible plan:
1) bcm43xx-mac80211 gets stable and merged, while bcm43xx is renamed to
bcm4301 and its PCI IDs list stripped down;
would sound a lot simpler. Even if the first plan could be better for users
and distributions. So I'd say, let's have a stable driver at least, before
to take a decision.
> What exactly do we gain from using the v4 firmware?
Other than crypto hardware, support for 802.11n devices, and maybe 802.11a
devices too (I started working on that but I'm not doing that right now).
> Anyway, I'm glad to hear we are making progress on this front.
> Good job, Larry!
Me too! Good job!
--
Ciao
Stefano
next prev parent reply other threads:[~2007-07-19 23:45 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
2007-07-19 22:26 ` Johannes Berg
2007-07-19 23:27 ` Stefano Brivio [this message]
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=20070720012714.0dc0298a@morte \
--to=stefano.brivio@polimi.it \
--cc=Larry.Finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).