summaryrefslogtreecommitdiff
path: root/hurd/faq/how_about_drivers.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'hurd/faq/how_about_drivers.mdwn')
-rw-r--r--hurd/faq/how_about_drivers.mdwn9
1 files changed, 5 insertions, 4 deletions
diff --git a/hurd/faq/how_about_drivers.mdwn b/hurd/faq/how_about_drivers.mdwn
index 0556fd28..0e1887ba 100644
--- a/hurd/faq/how_about_drivers.mdwn
+++ b/hurd/faq/how_about_drivers.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2009 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2009, 2013 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
@@ -10,8 +10,9 @@ License|/fdl]]."]]"""]]
[[!meta title="What drivers does GNU/Hurd have?"]]
-Currently, Mach integrates drivers from Linux 2.0 through some glue code. As
-it's very old, that limits hardware support a lot, of course. We are however
-working on using the DDE toolkit to run linux drivers in userland processes,
+Currently, for disks Mach integrates drivers from Linux 2.0 through some
+[[community/gsoc/project_ideas/driver_glue_code]]. As it's very old, that
+limits hardware support a lot, of course. For network boards, we use the
+[[DDE]] toolkit to run linux drivers in userland processes,
which provides both long-term support for new hardware and safety against driver
bugs.