[[!meta copyright="Copyright © 2009, 2010 Free Software Foundation, Inc."]]
[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]]
-
[[community/gsoc/project ideas/driver glue code]]
-
[[open issues/user-space device drivers]]
-
[[open issues/device drivers and io systems]]
-
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, http://os.inf.tu-dresden.de/pipermail/l4-hackers/2009/004291.html
Structural overview of the components.
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.).