From: Pavel Roskin <proski@gnu.org>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
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:52:34 -0400 [thread overview]
Message-ID: <1150347154.26487.30.camel@dv> (raw)
In-Reply-To: <4807377b0606121710j5be6ce0fhac71b69bf4dce2c2@mail.gmail.com>
On Mon, 2006-06-12 at 17:10 -0700, Jesse Brandeburg wrote:
> 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.
I believe the right solution would be to do it in userspace. The kernel
should not be making decisions which driver is _better_ for the device.
I'm yet to see any serious arguments why the kernel should be doing it.
As for non-working driver, this should be reported with sufficient
details. I haven't seen any detailed reports of this problem.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-06-15 4:52 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 ` Pavel Roskin [this message]
2006-06-15 4:45 ` [PATCH 2.6.17-rc6] " 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=1150347154.26487.30.camel@dv \
--to=proski@gnu.org \
--cc=davej@redhat.com \
--cc=faidon@cube.gr \
--cc=hermes@gibson.dropbear.id.au \
--cc=jesse.brandeburg@gmail.com \
--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 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).