From: Miles Lane <miles@megapathdsl.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug TTD
Date: Tue, 09 Jan 2001 06:55:14 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97902342318736@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97901650309422@msgid-missing>
Hmm. I assume that by "finish this thing", you mean the
generic portion of hotplug support. There are obviously
boatloads of changes needed in all the hotplug bus trees
and for all the hotpluggable devices.
The respective development communities will need to
enumerate the requirements for their areas (this IS
an invitation):
SCSI
Fusion MPT?
I2O?
IrDA
FireWire
PCMCIA/PC-Card
- Network adapter cards
- SCSI adapter cards
- USB host-controller cards
- Wireless network adapter cards
- ISDN adapter -- AVM A1 PCMCIA (Fritz)
Wireless Networking
PCI
USB
A somewhat tangential project is porting support for
all the devices covered by the pcmcia-cs package into
the kernel tree. This project also includes working
out all the usermode utility and configuration support
issues. Currently, the pcmcia-cs configuration does
not work for the native kernel drivers in 2.4.0
(yenta, 3c59x, etc).
I would prefer to see default configuration files live
in the kernel tree and be installed by the kernel
installation process when PCMCIA/Cardbus support is
selected. Ideally, the necessary usermode support
utilities would be disseminated in the same way that
ksymoops and modutils are now.
Other thoughts?
Miles
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2001-01-09 6:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 4:59 hotplug TTD Morton, Andrew [WOLL:4009-M:EXCH]
2001-01-09 5:47 ` Miles Lane
2001-01-09 6:55 ` Miles Lane [this message]
2001-01-09 8:49 ` Adam J. Richter
2001-01-09 17:09 ` David Brownell
2001-01-09 17:38 ` David Brownell
2001-01-10 6:20 ` Grover, Andrew
2001-01-10 6:34 ` Grover, Andrew
2001-01-10 10:58 ` Andrew Morton
2001-01-10 10:58 ` Andrew Morton
2001-01-10 10:59 ` Andrew Morton
2001-01-11 16:10 ` David Brownell
2001-01-11 16:40 ` David Brownell
2001-01-11 17:18 ` David Hinds
2001-01-11 18:04 ` David Brownell
2001-01-12 0:09 ` Grover, Andrew
2001-01-12 0:33 ` Grover, Andrew
2001-01-12 1:13 ` Grover, Andrew
2001-01-12 12:51 ` Andrew Morton
2001-01-12 16:42 ` David Brownell
2001-01-12 17:37 ` David Brownell
2001-01-12 23:45 ` Keith Owens
2001-01-13 18:54 ` David Brownell
2001-01-13 23:25 ` Keith Owens
2001-02-03 23:37 ` Miles Lane
2001-02-03 23:48 ` Keith Owens
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=marc-linux-hotplug-97902342318736@msgid-missing \
--to=miles@megapathdsl.net \
--cc=linux-hotplug@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).