From: "John W. Linville" <linville@tuxdriver.com>
To: Faidon Liambotis <faidon@cube.gr>
Cc: Dave Jones <davej@redhat.com>,
netdev@vger.kernel.org, proski@gnu.org,
hermes@gibson.dropbear.id.au
Subject: Re: [PATCH 2.6.17-rc6] Remove Prism II support from Orinoco
Date: Mon, 12 Jun 2006 11:24:39 -0400 [thread overview]
Message-ID: <20060612152434.GA14851@tuxdriver.com> (raw)
In-Reply-To: <20060611224954.GA2880@divinity>
On Mon, Jun 12, 2006 at 01:49:54AM +0300, Faidon Liambotis wrote:
> Having two drivers supporting the same set of hardware seems pretty
> pointless to me. Plus, it confuses hotplugging/automatic detection.
This subject comes-up from time to time. In fact, I'm pretty sure
it came-up very recently w.r.t. orinoco and hostap.
The consensus seems to be that drivers should have IDs for all devices
they support, even if that means that some devices are supported by
multiple drivers. This leaves the choice of which driver to use in
the hands of the user and/or distro.
If the Orinoco guys want this patch, I'll consider it. Otherwise,
I'm not inclined to take it.
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-06-12 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-10 17:50 [PATCH 2.6.17-rc6] Remove Prism II support from Orinoco Faidon Liambotis
2006-06-10 18:08 ` Dave Jones
2006-06-11 22:27 ` Dave Jones
2006-06-11 22:40 ` Dave Jones
2006-06-11 22:31 ` Kyle McMartin
2006-06-11 23:08 ` Dave Jones
2006-06-11 22:49 ` Faidon Liambotis
2006-06-12 15:24 ` John W. Linville [this message]
2006-06-12 15:39 ` Faidon Liambotis
2006-06-12 20:55 ` Dave Jones
2006-06-13 0:10 ` Jesse Brandeburg
2006-06-13 4:20 ` Stephen Hemminger
2006-06-13 4:30 ` Faidon Liambotis
2006-06-14 11:53 ` Jiri Benc
2006-06-15 4:52 ` [PATCH 2.6.17-rc6] " Pavel Roskin
2006-06-15 4:45 ` Pavel Roskin
2006-06-15 5:15 ` Faidon Liambotis
2006-06-15 20:07 ` John W. Linville
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=20060612152434.GA14851@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davej@redhat.com \
--cc=faidon@cube.gr \
--cc=hermes@gibson.dropbear.id.au \
--cc=netdev@vger.kernel.org \
--cc=proski@gnu.org \
/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).