From: Stefano Brivio <stefano.brivio@polimi.it>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
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 05:09:32 +0200 [thread overview]
Message-ID: <20070720050932.5052468c@morte> (raw)
In-Reply-To: <46A01209.4030200@lwfinger.net>
On Thu, 19 Jul 2007 20:38:17 -0500
Larry Finger <larry.finger@lwfinger.net> wrote:
> 4. Once bcm43xx-mac80211 gets merged to mainline, then Michael's driver
> should become bcm43xx and my driver gets its PCI IDs stripped to the
> 802.11b-only devices and once again becomes bcm4301. This name change for
> Michael's driver would cause some disruption for current users as their
> firmware would have the wrong name/version. That might be too much of a
> problem.
No, as long as we preserve the current firmware naming scheme. Some
distributions are already shipping both the softmac and the mac80211 based
drivers, with fwcutter installation scripts meant for dealing with this.
Some clear printk's in both drivers should do the rest.
--
Ciao
Stefano
next prev parent reply other threads:[~2007-07-20 3:13 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
2007-07-20 1:38 ` Larry Finger
2007-07-20 3:09 ` Stefano Brivio [this message]
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=20070720050932.5052468c@morte \
--to=stefano.brivio@polimi.it \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--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).