diff options
| author | antrik <antrik@users.sf.net> | 2009-03-10 07:46:17 +0100 |
|---|---|---|
| committer | antrik <antrik@users.sf.net> | 2009-03-10 23:56:48 +0100 |
| commit | 5d9917be086fddec2c55f460955cbd7a63e2aadd (patch) | |
| tree | e2c258e92c40a1d7be926af92267fbc3ba024314 | |
| parent | e38135b1f0d40ce8d0fccff875979218209b6efb (diff) | |
Glue code GSoC task: More explicitely suggest using ddekit
| -rw-r--r-- | community/gsoc/project_ideas/driver_glue_code.mdwn | 7 |
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 2f0a0b59..7e6d9598 100644 --- a/community/gsoc/project_ideas/driver_glue_code.mdwn +++ b/community/gsoc/project_ideas/driver_glue_code.mdwn @@ -21,8 +21,11 @@ solution, but works quite OK, except that the drivers are very old. The goal of 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. -Using [ddekit](http://demo.tudos.org/dsweeper_tutorial.html) instead of our -own glue code can be explored as a possible alternative approach. +While it would be certainly possible to create custom glue code again, a more +sustainable and probably also easier approch is to use +[ddekit](http://demo.tudos.org/dsweeper_tutorial.html) 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. This is a doable, but pretty involved project. Experience with driver programming under Linux (or BSD) is a must. (No Hurd-specific knowledge is |