summaryrefslogtreecommitdiff
path: root/hurd/faq/how_about_drivers.mdwn
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2013-03-15 14:46:44 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2013-03-15 14:46:44 +0100
commite113e5011c85c82cc473104d211d7d0765840c15 (patch)
tree6b2295a34355956e21bb4a75150056acdfc8b9db /hurd/faq/how_about_drivers.mdwn
parentfffec9e8a6f3ada8182cb170d69754ce65664147 (diff)
update faq
Diffstat (limited to 'hurd/faq/how_about_drivers.mdwn')
-rw-r--r--hurd/faq/how_about_drivers.mdwn6
1 files changed, 3 insertions, 3 deletions
diff --git a/hurd/faq/how_about_drivers.mdwn b/hurd/faq/how_about_drivers.mdwn
index 0556fd28..689dd807 100644
--- a/hurd/faq/how_about_drivers.mdwn
+++ b/hurd/faq/how_about_drivers.mdwn
@@ -10,8 +10,8 @@ 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 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.