From: Larry Finger <larry.finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Pavel Roskin <proski@gnu.org>, Ehud Gavron <gavron@Wetwork.Net>,
Broadcom Linux <bcm43xx-dev@lists.berlios.de>,
wireless <linux-wireless@vger.kernel.org>,
Stefano Brivio <stefano.brivio@polimi.it>,
Michael Buesch <mb@bu3sch.de>
Subject: Re: bcm4301: A mac80211 driver using V3 firmware
Date: Fri, 20 Jul 2007 15:41:24 -0500 [thread overview]
Message-ID: <46A11DF4.5090307@lwfinger.net> (raw)
In-Reply-To: <20070720180558.GG7428@tuxdriver.com>
John W. Linville wrote:
>
> ACK...fwiw, I like the "b43" name suggestion. I wonder if that is
> too prone to confusion w/ "b44"? Probably no worse than "ixgb" vs
> "cxgb3" or "e100" vs "e1000" I suppose.
Today's discussion was very useful for me - I picked up two suggestions that I have or will be
putting into the code.
1. The drivers that use V3 firmware will get a default fwpostfix value of ".fw3". If the resulting
name fails, it will fallback to a blank value for fwpostfix. Of course, if a value is supplied, it
will override the default.
2. Any b-only driver will contain an alternate PCI ID table that can be selected by using the
appropriate module option (not yet named). If that option is selected, the driver will load a
combined b/g table of ID's. This way, it will be easy to supply a work-around for any user that
cannot get the default 802.11g driver to work. In addition, this fix will not require mucking with
rc.local.
Larry
next prev parent reply other threads:[~2007-07-20 20:41 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
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 [this message]
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=46A11DF4.5090307@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=gavron@Wetwork.Net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=proski@gnu.org \
--cc=stefano.brivio@polimi.it \
/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).