aboutsummaryrefslogtreecommitdiff
path: root/faq/support/0-drivers.mdwn
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2013-03-28 23:29:24 +0100
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2013-03-28 23:29:24 +0100
commit211d4f0231ecc967bea385e3bed637aaff3d0fc5 (patch)
tree6bfc65c4441383338a85b2900501eb4da8285e8c /faq/support/0-drivers.mdwn
parentde5e67741f8e5926a4327d24b73b1a851e5539aa (diff)
parent7c90e65e25f673a9c621c6102ee3d7c130160b01 (diff)
downloadweb-211d4f0231ecc967bea385e3bed637aaff3d0fc5.tar.gz
web-211d4f0231ecc967bea385e3bed637aaff3d0fc5.tar.bz2
web-211d4f0231ecc967bea385e3bed637aaff3d0fc5.zip
Merge branch 'master' of git.savannah.gnu.org:/srv/git/hurd/web
Conflicts: faq/issues/got_a_db_prompt.mdwn
Diffstat (limited to 'faq/support/0-drivers.mdwn')
-rw-r--r--faq/support/0-drivers.mdwn3
1 files changed, 2 insertions, 1 deletions
diff --git a/faq/support/0-drivers.mdwn b/faq/support/0-drivers.mdwn
index 1c6f58dc..54b2d744 100644
--- a/faq/support/0-drivers.mdwn
+++ b/faq/support/0-drivers.mdwn
@@ -15,7 +15,8 @@ Currently, for disks Mach integrates drivers from Linux 2.0 through some
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. Xen is also supported, both blkfront and netfront.
+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