From: John Weber <john.weber@linux.org>
To: linux-kernel@vger.kernel.org
Subject: Linux PCMCIA
Date: Thu, 25 Jul 2002 18:16:39 -0400 [thread overview]
Message-ID: <3D4078C7.4010304@linux.org> (raw)
I noticed on the kernel status doc that a revamp of kernel pcmcia is in
the works. Can anyone elaborate?
For example, does this mean that 16-bit PCMCIA cards will use hotplug?
Does this mean that 32-bit cards will stop requiring cardmgr to simply
bind devices to drivers (is it too much to ask that the driver know what
it drives :)? The only card of mine (and I have a few 3coms, xircoms,
lucents) that I think works sanely is my xircom 32-bit cardbus card...
it would be nice if they all worked that way. Even though I know that
this will not be possible for the 16-bit pcmcia cards, IMHO atleast all
the hotplug devices should use ONE daemon.
I'm curious and excited by the prospect... if there is anything I can do
to help (even as a newbie I can certainly help change
unregister/register functions or add any device tables, etc), please let
me know.
next reply other threads:[~2002-07-25 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-25 22:16 John Weber [this message]
2002-07-26 9:03 ` Linux PCMCIA David Woodhouse
2002-07-26 10:47 ` Alan Cox
2002-07-29 9:28 ` David Woodhouse
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=3D4078C7.4010304@linux.org \
--to=john.weber@linux.org \
--cc=linux-kernel@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