All of lore.kernel.org
 help / color / mirror / Atom feed
From: john slee <indigoid@higherplane.net>
To: "Dmitry A. Fedorov" <D.A.Fedorov@inp.nsk.su>
Cc: Balbir Singh <balbir_soni@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Is it useful to support user level drivers
Date: Thu, 21 Jun 2001 23:50:25 +1000	[thread overview]
Message-ID: <20010621235025.J30872@higherplane.net> (raw)
In-Reply-To: <Pine.SGI.4.10.10106211833390.3193032-100000@Sky.inp.nsk.su>

On Thu, Jun 21, 2001 at 06:38:09PM +0700, Dmitry A. Fedorov wrote:
> kernel module to delivery hardware interrupts to user space
> programs. Hardware interrupts (IRQ) are accessible by
> character devices /dev/irq[0-15]. Interrupts delivered by
> signals and select(2)/poll(2)

i believe libgpio uses the existing usb/iee1394/serial/parallel
interfaces to provide a limited userspace driver capability.  gphoto2
uses this to support a LOT of digital cameras entirely in userspace...

obviously this concept isn't covering everything but it sure covers a
lot of bases.  also depends on what you understand a "driver" to be...
from a "common user"'s perspective it just means "it makes my WinWidget
work!"

it's similar to what you describe above in that there's a kernel
interface, but it's more specific than /dev/irq5.  this is good in that
you don't want a different usb driver for every userspace usb device
driver...

http://sourceforge.net/projects/gphoto/ (i think)

j.

-- 
"Bobby, jiggle Grandpa's rat so it looks alive, please" -- gary larson

  reply	other threads:[~2001-06-21 13:34 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21 10:41 Is it useful to support user level drivers Balbir Singh
2001-06-21 10:55 ` Tim Waugh
2001-06-21 11:04 ` Alan Cox
2001-06-21 12:43   ` Balbir Singh
2001-06-21 13:27     ` Alan Cox
2001-06-28 22:52     ` Pavel Machek
2001-06-21 12:45   ` Dmitry A. Fedorov
2001-06-21 13:24     ` Oliver Neukum
2001-06-21 14:46       ` Dmitry A. Fedorov
2001-06-21 15:19         ` Oliver Neukum
2001-06-22  4:19           ` Dmitry A. Fedorov
2001-06-22  7:28             ` Balbir Singh
2001-06-21 16:34         ` Abramo Bagnara
2001-06-21 17:27           ` Alan Cox
2001-06-21 19:59             ` Abramo Bagnara
2001-06-21 20:40               ` Richard B. Johnson
2001-06-21 20:54                 ` Abramo Bagnara
2001-06-21 21:09               ` Oliver Neukum
2001-06-28 22:57             ` Pavel Machek
2001-06-21 13:28     ` Alan Cox
2001-06-21 14:03       ` Matthias Urlichs
2001-06-28 22:54         ` Pavel Machek
2001-06-21 14:20       ` Dmitry A. Fedorov
2001-06-21 11:38 ` Dmitry A. Fedorov
2001-06-21 13:50   ` john slee [this message]
2001-06-21 13:58     ` Matthias Urlichs
2001-06-21 14:21       ` john slee
2001-06-28 22:51 ` Pavel Machek
     [not found] <mailman.993156181.18994.linux-kernel2news@redhat.com>
2001-06-21 22:06 ` Pete Zaitcev
2001-06-21 22:20   ` David S. Miller
2001-06-21 23:09     ` Mike Mackovitch
2001-06-21 23:22       ` David S. Miller
2001-06-21 23:50         ` Mike Mackovitch
2001-06-22  0:36           ` David S. Miller
2001-06-21 23:40   ` Richard B. Johnson
2001-06-22  0:30     ` Anders Larsen
2001-06-22  0:43       ` Richard B. Johnson
2001-06-25  0:06         ` Anders Larsen

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=20010621235025.J30872@higherplane.net \
    --to=indigoid@higherplane.net \
    --cc=D.A.Fedorov@inp.nsk.su \
    --cc=balbir_soni@yahoo.com \
    --cc=linux-kernel@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.