From: "John W. Linville" <linville@tuxdriver.com>
To: Pavel Roskin <proski@gnu.org>
Cc: 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>,
Larry Finger <larry.finger@lwfinger.net>
Subject: Re: bcm4301: A mac80211 driver using V3 firmware
Date: Fri, 20 Jul 2007 14:05:58 -0400 [thread overview]
Message-ID: <20070720180558.GG7428@tuxdriver.com> (raw)
In-Reply-To: <1184954268.1962.43.camel@dv>
On Fri, Jul 20, 2007 at 01:57:48PM -0400, Pavel Roskin wrote:
> On Fri, 2007-07-20 at 09:33 -0700, Ehud Gavron wrote:
> > The driver should have a name that reflects its use and capabilities.
>
> Not necessarily. End users should be shielded from such details by
> distributions. Do you know the name of the Windows driver for your
> network card? Does it reflect "its use and capabilities"?
>
> Now, if we are talking about power users, who can occasionally recompile
> the kernel or install a program not from the distribution, they would be
> helped by reasonable names of the drivers.
>
> Also, distribution maintainers would feel better if the drivers are not
> renamed, so that /etc/modprobe.d/ doesn't need to be scanned for the old
> names on kernel upgrade.
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.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-07-20 18:33 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 [this message]
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=20070720180558.GG7428@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=gavron@Wetwork.Net \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.