From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: BoF on hotplugging - summary
Date: Wed, 06 Nov 2002 18:49:00 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103660890017373@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103281861328682@msgid-missing>
> A suggestion was made that a demon should be introduced. That was not discussed
> fully. Later discussion with the X people which are to be continued shows
> that the X people would want to introduce an X extension for device discovery
> and notification issues.
How about adding a new kind of hotplug agent: daemons
that see events delivered through a filesystem socket or
pipe, like /var/run/hotplug/input.agent? Simple to add.
Easy to integrate with, and lots of people are already
working with similar models. It'd move the X discussions
to a more useful stage: here's the device, now what? :)
I suspect few of those daemons would ever be "part of"
the hotplug system, except in terms of hearing from it
through the /var/run/hotplug/*.agent files.
> Information needed by user space:
> Items of consensus:
> - physical path and all available device ids must be delivered
I'll submit a 2.5 patch to do that for USB, which currently
does not expose that through hotplug. (PCI does.) This is a
simple thing to add to 2.4.20, too, so updated user mode tools
(that know about physical paths) wouldn't need 2.5 to run.
- Dave
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
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
prev parent reply other threads:[~2002-11-06 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 22:00 BoF on hotplugging - summary Oliver Neukum
2002-09-23 22:14 ` Brad Hards
2002-09-23 22:58 ` Greg KH
2002-09-23 23:00 ` Greg KH
2002-09-23 23:15 ` Tim Jansen
2002-11-06 18:49 ` David Brownell [this message]
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-103660890017373@msgid-missing \
--to=david-b@pacbell.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).