From: David Gibson <hermes@gibson.dropbear.id.au>
To: Faidon Liambotis <paravoid@debian.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2.6.23 3/3] [wireless] orinoco: create a Kconfig option for Prism2
Date: Mon, 23 Jul 2007 11:42:10 +1000 [thread overview]
Message-ID: <20070723014210.GB3272@localhost.localdomain> (raw)
In-Reply-To: <20070722131751.GA3009@void.cube.gr>
On Sun, Jul 22, 2007 at 04:17:51PM +0300, Faidon Liambotis wrote:
> Since v2.6.14, Prism 2/2.5/3 devices are better supported using the HostAP
> driver, which was made to work with these exclusively.
> Having the same IDs supported by orinoco too confuses users who have both
> drivers compiled in or as modules who expect hostap to drive the device.
>
> Telling users to echo to /sys/bus/pci/drivers/*/unbind and bind is not
> exactly user-friendly.
>
> Create an option to disable support for Prism devices in orinoco driver which
> disabled the IDs for the PCMCIA module and creates a Kconfig dependency for
> the Prism PCI modules.
I very much dislike this being a compile time only CONFIG option. A
module parameter which enables or disables the device IDs would be
much nicer, if possible. It can default to off (orinoco will not
claim Prism cards).
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2007-07-23 1:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 13:17 [PATCH 2.6.23 3/3] [wireless] orinoco: create a Kconfig option for Prism2 Faidon Liambotis
2007-07-22 17:14 ` Pavel Roskin
2007-07-23 22:07 ` Faidon Liambotis
2007-07-25 5:30 ` Pavel Roskin
2007-07-25 6:19 ` Faidon Liambotis
2007-07-25 16:32 ` Pavel Roskin
2007-08-01 3:33 ` Jouni Malinen
2007-08-01 5:55 ` Pavel Roskin
2007-07-23 1:42 ` David Gibson [this message]
2007-07-23 6:10 ` Pavel Roskin
2007-07-23 6:20 ` David Gibson
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=20070723014210.GB3272@localhost.localdomain \
--to=hermes@gibson.dropbear.id.au \
--cc=linux-wireless@vger.kernel.org \
--cc=paravoid@debian.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