Date: Sat, 5 May 2007 23:00:26 +0100
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Clifford Wolf <clifford@clifford.at>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Interrupt-Handling in User Space
Message-ID: <20070505230026.4b2f4030@the-village.bc.nu>
In-Reply-To: <20070505191707.GA9300@clifford.at>
References: <20070505191707.GA9300@clifford.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 721
Lines: 14

> afaics there is no mechanism in the official kernel tree to handle
> interrupts in user space yet. I'd need that for an embedded project I'm

Its basically not possible to do with most hardware because you get
deadlocks when there are shared interrupts.

However see drivers/uio in the current GIT tree (or recent -mm kernels),
that assumes you write a truely minimal IRQ handler/board driver in the
kernel and it then exposes the memory spaces and IRQ stream to user space.
-
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/