[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45811D0F.2070705@argo.co.il>
Date: Thu, 14 Dec 2006 11:44:47 +0200
From: Avi Kivity <avi@...o.co.il>
To: Greg KH <greg@...ah.com>
CC: linux-kernel@...r.kernel.org, tglx@...utronix.de
Subject: Re: Userspace I/O driver core
Greg KH wrote:
> A large number of people have expressed interest recently in the
> userspace i/o driver core which allows userspace drivers to be written
> to handle some types of hardware.
>
> Right now the UIO core is working and in the -mm releases. It's been
> rewritten from the last time patches were posted to lkml and is much
> simpler. It also includes full documentation and two example drivers
> and two example userspace programs that test those drivers.
>
> But in order to get this core into the kernel tree, we need to have some
> "real" drivers written that use it. So, for anyone that wants to see
> this go into the tree, now is the time to step forward and post your
> patches for hardware that this kind of driver interface is needed.
>
>
[...]
> If anyone has any questions on how to use this interface, or anything
> else about it, please let me and Thomas know.
>
>
I understand one still has to write a kernel driver to shut up the irq.
How about writing a small bytecode interpreter to make event than
unnecessary?
The userspace driver would register a couple of bytecode programs:
is_interrupt_pending() and disable_interrupt(), which the uio framework
would call when the interrupt fires.
The bytecode could reuse net/core/filter.c, with the packet replaced by
the mmio or ioregion, or use something new.
--
error compiling committee.c: too many arguments to function
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists