From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: definition of terms
Date: Fri, 09 Feb 2001 17:59:08 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98174260915753@msgid-missing> (raw)
There's "function" too. "Physical device" is something I can pick
up, but when I plug it in it may do several things. PCI cards
can integrate several functions (up to 8?) and USB devices
can have several "interfaces" (up to 255) or be parts of compound
devices (most software will ignore that last). Examples (real):
- Device: Cardbus
* Functions 1,2: USB OHCI host controller
* Function 3: USB EHCI host controller
- Device: USB
* Function 1: audio speaker
* Function 2: three buttons
- Compound USB device (integrates a hub):
* Device 1: USB Hub (single function)
* Device 2: USB Keyboard (single function)
Right now, /proc/bus/usb names devices, while /proc/bus/pci
names functions. In an ideal world, we'd be consistent in those
two, and /proc/bus/pcmcia would also be consistent. (Also in
an ideal world, /proc/bus/usb would expose stable names based
on topology, not unstable ones based on current addresses.)
We report hotplug events not in terms of "physical device"
as you said, or (device) function as I might prefer ... but in
the granularity used by those /proc/bus names. Even in
kernels not configured with usbdevfs, and even though
multifunction USB devices should arguably get multiple
hotplug events. (It'd work better that way on systems
that don't configure usbdevfs, too.)
Your definition needs to be less precise, if it's to be accurate.
More general ... unless we change the code, which should
be a separate thread.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2001-02-09 17:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-98174260915753@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).