From: Larry Finger <Larry.Finger@lwfinger.net>
To: John Linville <linville@tuxdriver.com>, Michael Buesch <mb@bu3sch.de>
Cc: wireless <linux-wireless@vger.kernel.org>,
bcm43xx devel <Bcm43xx-dev@lists.berlios.de>
Subject: RFC: Future plans for bcm43xx-softmac
Date: Fri, 23 Mar 2007 12:37:51 -0500 [thread overview]
Message-ID: <4604106F.7080003@lwfinger.net> (raw)
I think we have a plan for the future of bcm43xx-softmac once the bcm43xx-mac80211 version goes into
mainline. Unfortunately it cannot just be abandoned as there will be no support for 802.11b-only
devices in bcm43xx-mac80211.
The steps to be done are as follows:
1. Change the namespace from bcm43xx to bcm4301. This will both reflect the purpose of the changed
driver as well as prevent namespace collisions with the bcm43xx-mac80211 version in case both are
built into the kernel.
2. Modify bcm4301 to use mac80211 rather than softmac. Although this process has the potential for
introducing bugs into what is currently the stable version, it does allow the abandonment of softmac
with its deficiencies, many of which are essentially uncorrectable.
3. The PCI-ids recognized by bcm4301-mac80211 will be restricted to the 802.11b-only devices and the
configuration information will be modified.
Step 1 will be completed very soon and the appropriate patches will be submitted to Linville's
wireless-dev tree.
I will be working on step 2 in the coming months and will submit those patches to the list for
comments and testing. When ready, they too will be submitted to Linville. Once bcm43xx-mac80211 goes
into mainline, the step 3 patches will be submitted.
Please comment on this plan.
Thanks,
Larry
next reply other threads:[~2007-03-23 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-23 17:37 Larry Finger [this message]
2007-03-23 18:30 ` RFC: Future plans for bcm43xx-softmac Michael Buesch
2007-03-23 19:46 ` Stefano Brivio
2007-03-24 1:41 ` 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=4604106F.7080003@lwfinger.net \
--to=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).