From: Jeff Garzik <jgarzik@pobox.com>
To: jt@hpl.hp.com
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@brodo.de>
Subject: Re: [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support
Date: Tue, 08 Apr 2003 18:56:12 -0400 [thread overview]
Message-ID: <3E93538C.9010306@pobox.com> (raw)
In-Reply-To: <20030408223111.GA25785@bougret.hpl.hp.com>
Jean Tourrilhes wrote:
> Jeff Garzik wrote :
>>That was a big stumbling block when I last looked at the "big picture"
>>for pcmcia -- in-kernel drivers still required probe assistance from
>>userspace via the /etc/pcmcia/* bindings.
>
>
> No ! Please don't do that, it will only bring madness.
Nope. It's already a solved problem :) More below...
> Example :
> Lucent/Agere Orinoco wireless card :
> manfid 0x0156,0x0002
> possible drivers : wlan_cs ; orinoco_cs
> Intersil PrismII and clones (Linksys, ...) :
> manfid 0x0156,0x0002
> possible drivers : prism2_cs ; hostap_cs
>
> Please explain me in details how your stuff will cope with the
> above, and how to make sure the right driver is loaded in every case
> and how user can control this.
> If your scheme can't cope with the simple real life example
> above (I've got those cards on my desk, and those drivers on my disk),
> then it's no good to me.
These cases already exist for PCI, so pcmcia behavior should follow what
the kernel does when the PCI core sees such.
Jeff
next prev parent reply other threads:[~2003-04-08 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 22:31 [PATCHES 2.5.67] PCMCIA hotplugging, in-kernel-matching and depmod support Jean Tourrilhes
2003-04-08 22:56 ` Jeff Garzik [this message]
2003-04-09 0:05 ` Jean Tourrilhes
2003-04-09 6:38 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2003-04-08 20:56 Dominik Brodowski
2003-04-08 21:20 ` Jeff Garzik
2003-04-08 21:34 ` Dominik Brodowski
2003-04-08 23:01 ` Jeff Garzik
2003-04-09 19:48 ` Dominik Brodowski
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=3E93538C.9010306@pobox.com \
--to=jgarzik@pobox.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
/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