All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Remove Prism II support from Orinoco
Date: Mon, 12 Jun 2006 21:20:48 -0700	[thread overview]
Message-ID: <20060613042048.GA14824@shell0.pdx.osdl.net> (raw)
In-Reply-To: <4807377b0606121710j5be6ce0fhac71b69bf4dce2c2@mail.gmail.com>

On 12/06/06 17:10 -0700, Jesse Brandeburg wrote:
> On 6/12/06, John W. Linville <linville@tuxdriver.com> 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.
> 
> my problem is that for my prism 2 adapter both drivers are loaded at
> which point neither of them works.  I'm running FC5, and i have to
> keep removing the orinoco*.ko files to keep them from loading, so I'm
> all for this patch.
> 

use blacklist in module config to block one.
Just put in /etc/modprobe.conf

blacklist orinoco

  reply	other threads:[~2006-06-13  4:20 UTC|newest]

Thread overview: 20+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2006-06-13 18:24 Jar
2006-06-14 19:09 ` Mike Kershaw

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=20060613042048.GA14824@shell0.pdx.osdl.net \
    --to=shemminger@osdl.org \
    --cc=jesse.brandeburg@gmail.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.