From: Chris Hanson <cph@zurich.ai.mit.edu>
To: linux-hotplug@vger.kernel.org
Subject: Is there any docs or design guides for adding hotplugablity to drivers?
Date: Tue, 02 Jul 2002 02:32:50 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102557834910158@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102555728227620@msgid-missing>
Date: 01 Jul 2002 14:00:19 -0700
From: Mark Atwood <mra@pobox.com>
Other than just reading the source, of course.
I'm working on a Linux appliance, and I feel that using hotplug events
to signal things like moving in range of an 802.11 access point,
getting carrier on an ethernet port, and someone plugging a cable into
the serial port, would make a lot of stuff much much easier.
I suspect that a lot of this would be useful out in the "regular
linux" world as well. Especially the ethernet carrier detect. (Windows
can do it, and will invoke DHCP when you plug in an ethernet cable, it
would be nice if Linux can do the same.)
I'm working on this. I've already implemented code to do carrier
detect, although this only works on NICs that support MII.
(Unfortunately the Lucent Prism II doesn't support MII; if anyone
knows how to do carrier detect on non-MII NICs, I'd appreciate
learning how.) See the Debian package "laptop-net" for details:
http://packages.debian.org/unstable/admin/laptop-net.html
This package also handles configuration and so forth.
However, there are N such Debian packages, each with a different set
of features and a different configuration interface. What I'm
currently working on is an event daemon to allow the functionality in
these packages to be modularized. I plan to use this to provide a
uniform event-signalling mechanism for all sorts of things, including
networking and APM. The immediate application is a project underway
here at MIT to improve our laptop infrastructure. But the mechanism
is general enough to handle any kind of event.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2002-07-02 2:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 21:00 Is there any docs or design guides for adding hotplugablity to drivers? Mark Atwood
2002-07-02 2:23 ` Is there any docs or design guides for adding hotplugablity to David Brownell
2002-07-02 2:32 ` Chris Hanson [this message]
2002-07-02 3:37 ` Is there any docs or design guides for adding hotplugablity to drivers? Brad Hards
2002-07-02 4:52 ` Greg KH
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-102557834910158@msgid-missing \
--to=cph@zurich.ai.mit.edu \
--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).