summaryrefslogtreecommitdiff
path: root/faq/drivers.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'faq/drivers.mdwn')
-rw-r--r--faq/drivers.mdwn26
1 files changed, 26 insertions, 0 deletions
diff --git a/faq/drivers.mdwn b/faq/drivers.mdwn
new file mode 100644
index 00000000..197d47b7
--- /dev/null
+++ b/faq/drivers.mdwn
@@ -0,0 +1,26 @@
+[[!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
+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]]."]]"""]]
+
+[[!tag faq/support faq/_important]]
+
+[[!meta title="What drivers does GNU/Hurd have?"]]
+
+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 2.6.32 drivers in userland processes,
+which provides both long-term support for new hardware and safety against driver
+bugs. [[microkernel/mach/gnumach/ports/Xen]] is also supported, both blkfront
+and netfront.
+
+Note however that we have of course not tested all drivers, we obviously don't
+even have all kinds of hardware. So we can not promise that they will all
+work. What probably works for sure is what we usually use: the rtl8139 or e1000
+drivers for instance.