All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Faidon Liambotis <faidon@cube.gr>, Dave Jones <davej@redhat.com>,
	netdev@vger.kernel.org, hermes@gibson.dropbear.id.au
Subject: Re: [PATCH 2.6.17-rc6] Remove Prism II support from Orinoco
Date: Thu, 15 Jun 2006 00:45:13 -0400	[thread overview]
Message-ID: <1150346713.26487.24.camel@dv> (raw)
In-Reply-To: <20060612152434.GA14851@tuxdriver.com>

Hello, John!

On Mon, 2006-06-12 at 11:24 -0400, John W. Linville wrote:
> 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.

I really appreciate your position in this regard.

The patch in question was never submitted to the orinoco mailing list.
I believe any such changes should be discussed by people using the
driver and participating in its development.  It's not some minor change
or API update.

I'm ready to consider disabling some ID's conditionally, primarily for
systems that cannot use udev.  But it's far from the top of my TODO
list.  And I'm not sure it would actually help users of desktop
distributions.

-- 
Regards,
Pavel Roskin


  parent reply	other threads:[~2006-06-15  4:45 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
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 [this message]
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=1150346713.26487.24.camel@dv \
    --to=proski@gnu.org \
    --cc=davej@redhat.com \
    --cc=faidon@cube.gr \
    --cc=hermes@gibson.dropbear.id.au \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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 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.