summaryrefslogtreecommitdiff
path: root/open_issues/dde.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2009-12-31 15:42:41 +0100
committerThomas Schwinge <thomas@schwinge.name>2009-12-31 15:42:41 +0100
commit7e65809229c18a4d798f3e305d5ad73e5d515d48 (patch)
tree9162224a27c88f9720d416fe8f8109cf20c44120 /open_issues/dde.mdwn
parent16dae1e1ca8f64b973d9b00297d403ed228980d1 (diff)
Been doin' some reading.
Diffstat (limited to 'open_issues/dde.mdwn')
-rw-r--r--open_issues/dde.mdwn15
1 files changed, 14 insertions, 1 deletions
diff --git a/open_issues/dde.mdwn b/open_issues/dde.mdwn
index 3d1de09a..096d532f 100644
--- a/open_issues/dde.mdwn
+++ b/open_issues/dde.mdwn
@@ -20,9 +20,22 @@ License|/fdl]]."]]"""]]
* <http://demo.tudos.org/dsweeper_tutorial.html>
+ Why device drivers in user space; different possibilities for getting
+ device drivers; DDE's origins and rationale.
+
* <http://wiki.tudos.org/DDE/DDEKit>
+ Structural overview of the components.
+
+
+# Discussion
+
+DDE essentially is a glue layer to embed Linux device drivers into another
+environement. In the DDE case, this *other environment* is a user-space task
+-- compared to the GNU Mach kernel having a *in-kernel* Linux 2.0 device
+drivers glue code (cf. paper by Goel et al.).
+
-# Sources
+# Source Code
* <http://www.inf.tu-dresden.de/index.php?node_id=1584&ln=en>