From: Oliver Neukum <oliver@neukum.name>
To: linux-hotplug@vger.kernel.org
Subject: BoF on hotplugging - summary
Date: Mon, 23 Sep 2002 22:00:20 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103281861328682@msgid-missing> (raw)
Hi people,
here's my summary on a BoF session during the recent Linuxkongress
in Cologne.
Regards
Oliver
BoF on USB and Hotplugging
Participants:
Brad Hards(USB), Tim Jansen(KDE), Oliver Neukum(USB), one unnamed and
largely silent GNOME coder and several other interested participants.
Unfortunately nobody of XFree was present.
Topics:
- definitions
- delivering events
- information needed by user space
- device numbers, names and associated stuff
Definitions: I remember nothing noteworthy
Delivering events:
General consensus was that there's nothing wrong in that regard.
The KDE and GNOME people would be quite happy with the hotplugging
scripts writing all information they have to a named pipe or something
similar. It seems that nobody really cares much about the exact mechanism.
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.
Information needed by user space:
Items of consensus:
- physical path and all available device ids must be delivered
- groupings of devices must be delivered
- most crucial item: user space needs a mapping between physical and logical device
- user space wants a device _name_
- driverfs and the input layer must be documented
A partial solution to the issues was found.
There needs to be a second kind of hotplugging event that is generated
upon "associating" a device to a driver
Device numbers, names and associated stuff
Items of consensus:
- device numbers are a bad idea
- there needs to be some "dynamic element"
There was absolute disagreement over devfs.
Oppinions ranged from "devfs must go away" to "hotplugging without
devfs is obviously stupid"
-------------------------------------------------------
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 reply other threads:[~2002-09-23 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 22:00 Oliver Neukum [this message]
2002-09-23 22:14 ` BoF on hotplugging - summary 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
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-103281861328682@msgid-missing \
--to=oliver@neukum.name \
--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).