From: =?iso-8859-1?q?Hans-J=FCrgen_Koch?= <hjk@linutronix.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Userspace I/O driver core
Date: Thu, 14 Dec 2006 11:25:14 +0100
User-Agent: KMail/1.9.5
References: <20061214010608.GA13229@kroah.com> <45811D0F.2070705@argo.co.il>
In-Reply-To: <45811D0F.2070705@argo.co.il>
Organization: Linutronix
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612141125.14777.hjk@linutronix.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1018
Lines: 27

Am Donnerstag, 14. Dezember 2006 10:44 schrieb Avi Kivity:

> 
> 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.
> 

I think this would be overkill. The kernel module you have to write
is _really_ very simple. And it has to be written only once, so even
a manufacturer who employs no experienced kernel developers can
easily outsource that task.

Hans

-
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/