Message-ID: <45811D0F.2070705@argo.co.il>
Date: Thu, 14 Dec 2006 11:44:47 +0200
From: Avi Kivity <avi@argo.co.il>
User-Agent: Thunderbird 1.5.0.8 (X11/20061107)
MIME-Version: 1.0
To: Greg KH <greg@kroah.com>
CC: linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: Userspace I/O driver core
References: <20061214010608.GA13229@kroah.com>
In-Reply-To: <20061214010608.GA13229@kroah.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1662
Lines: 42

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/