linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <Oliver.Neukum@lrz.uni-muenchen.de>
To: linux-hotplug@vger.kernel.org
Subject: definition of terms (was: Re: Adding PCMCIA support to the kernel tree -- developers needed.)
Date: Fri, 09 Feb 2001 17:03:30 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98173830701779@msgid-missing> (raw)

> > I fear we are being sucked down by semantics.
>
> You can't get away from that in design discussions.  Gotta
> eliminate confusions up front.
>
> And this application structure is very important.  You can't
> design a "system" without knowing the ways people interact
> with it ... /dev/NNN is no more than one part of a 1970s
> solution to a simpler system problem than we have today.
> We can still use it, but it's not a straightjacket to live in.

OK. Let me list all terms used up to now and give a preliminary definition.


'physical device' - hardware, in this context usually hotpluggable

'hotplug event' - any event relating to a hotpluggable device which the 
kernel may report to user space

'user space agent' - task the kernel spawns in reaction to a hotplug event

'interface driver' - a kernel space driver that user space can use to talk to 
a physical devices. There may be more than one interface driver per physical 
device, or in rare cases, none.

'logical driver' - interface the user space agent may set up, which allows 
the rest of user space to use the services a physical device offers, optional

'device name'  - a name userspace uses to identify the interface driver

'stable name' - a device name that depends on a unique characteristic of a 
device or on the way a device is connected to a bus

'physical location' - a description of how a device is connected to a bus.
at one time a connected physical device has one physical location and there 
is a maximum of one device to a physical location

Now to an example:

physical device: a USB scanner

hotplug event: scanner is plugged in + possibly others (to be decided)

user space agent: /sbin/hotplug + scripts called by it

interface driver: usbscanner.o

logical driver: epson backend of SANE

I introduced the term 'interface driver' because it is needed.

	HTH
		Oliver

_______________________________________________
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:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09 17:03 Oliver Neukum [this message]
2001-02-09 17:30 ` definition of terms (was: Re: Adding PCMCIA support to the kernel tree -- developers needed.) David Hinds
2001-02-09 18:53 ` Vojtech Pavlik
2001-02-10 10:30 ` Oliver Neukum

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-98173830701779@msgid-missing \
    --to=oliver.neukum@lrz.uni-muenchen.de \
    --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).