summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/driver_glue_code.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'community/gsoc/project_ideas/driver_glue_code.mdwn')
-rw-r--r--community/gsoc/project_ideas/driver_glue_code.mdwn7
1 files changed, 5 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/driver_glue_code.mdwn b/community/gsoc/project_ideas/driver_glue_code.mdwn
index e1b8d22e..9c063e9f 100644
--- a/community/gsoc/project_ideas/driver_glue_code.mdwn
+++ b/community/gsoc/project_ideas/driver_glue_code.mdwn
@@ -11,7 +11,7 @@ is included in the section entitled
[[!meta title="New Driver Glue Code"]]
-Although a driver framework in userspace would be desirable, presently the Hurd
+Although a driver framework in user space would be desirable, presently the Hurd
uses kernel drivers in the microkernel,
[[GNU_Mach|microkernel/mach/gnumach]]. (And changing this would be far beyond a
GSoC project...)
@@ -23,7 +23,7 @@ this project is to redo the glue code, so we can use drivers from current Linux
versions, or from one of the free BSD variants.
While it would be certainly possible to create custom glue code again, a more
-sustainable and probably also easier approch is to use
+sustainable and probably also easier approach is to use
[[DDE]] instead -- it already
does the hard work of providing an environment where the foreign drivers can
run, and has the additional advantage of being externally maintained.
@@ -44,3 +44,6 @@ ethernet) from a recent system, and try to port it to run in the existing
driver framework in GNU Mach. Completing the port might be too involved for the
exercise; but it's pretty likely that you will find something else to improve
in the glue code while working on this...
+
+*Status*: [[Zheng Da|zhengda]] is working on DDE, and has mostly completed the
+initial port.