summaryrefslogtreecommitdiff
path: root/open_issues/user-space_device_drivers.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2009-07-21 20:06:47 +0200
committerThomas Schwinge <tschwinge@gnu.org>2009-07-21 20:06:47 +0200
commitee171038e27e5288e6606f8affb20faabd6daf40 (patch)
tree44cbc2188176ab7ca16e4da776e3b0029c148730 /open_issues/user-space_device_drivers.mdwn
parent4330627c10314d5495b7e93989b2a608d705de09 (diff)
open_issues/user-space_device_drivers: Event objects.
Diffstat (limited to 'open_issues/user-space_device_drivers.mdwn')
-rw-r--r--open_issues/user-space_device_drivers.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/open_issues/user-space_device_drivers.mdwn b/open_issues/user-space_device_drivers.mdwn
index 43795705..33e75942 100644
--- a/open_issues/user-space_device_drivers.mdwn
+++ b/open_issues/user-space_device_drivers.mdwn
@@ -27,6 +27,11 @@ Also see [[device drivers and IO systems]].
* *Omega0* paper defines an interface.
+ * As is can be read in the *Mach 3 Kernel Principles*, there is an *event
+ object* facility in Mach that can be used for having user-space tasks react
+ to IRQs. However, at least in GNU Mach, that code (`kern/eventcount.c`)
+ doesn't seem functional at all and isn't integrated properly in the kernel.
+
## DMA
* Security considerations.