From: Brad Hards <bhards@bigpond.net.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: BoF on hotplugging - summary
Date: Mon, 23 Sep 2002 22:14:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103281967929700@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103281861328682@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 24 Sep 2002 08:00, Oliver Neukum wrote:
> - groupings of devices must be delivered
This is an important issue that might be worth expanding on.
Some of the newer devices have multiple logical "interfaces" (read this in a
loose sense, not meant to equal USB interfaces). Somethimes the device offers
all the interfaces at once, sometimes you can choose one or the other.
USB example - speakers. There is an audio interface (usually with some
selection of sampling rates, which you might consider to be a choose 1 of N
interfaces) and a HID interface (for button controlling volume, etc).
We need some way of selecting the interfaces we want, and associating them
into sensible groups (so that if I have two speakers, and a multimedia
keyboard; I can get the volume controls on each set of speakers to only
control those speakers, and the volume control keys on my keyboard to control
the built-in (PCI bus) soundcard.
This is really a policy thing, and the kernel is probably provding enough when
we have topology, but there is a lot of userspace work to be done.
> - driverfs and the input layer must be documented
I'm working on the input layer docs now.
Greg: do you know of any plans to document how userspace should use driverfs?
Thanks for writing this up Oliver.
Brad
- --
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9j5ItW6pHgIdAuOMRAli6AKCAWxa4C1hHGwOII0zXExIuSvkIwwCdGVd4
7Wa+Bl46HL2f53soQNWIRXM=OSwE
-----END PGP SIGNATURE-----
-------------------------------------------------------
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-09-23 22:14 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 [this message]
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-103281967929700@msgid-missing \
--to=bhards@bigpond.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.