aboutsummaryrefslogtreecommitdiff
path: root/faq/support/0-drivers.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@codesourcery.com>2013-03-26 15:49:59 +0100
committerThomas Schwinge <thomas@codesourcery.com>2013-03-26 15:49:59 +0100
commit7c90e65e25f673a9c621c6102ee3d7c130160b01 (patch)
treeb399b10e23f3194d70326eac190f74de473d60d5 /faq/support/0-drivers.mdwn
parentab11a8b78ca03dede4b29bbb7a04dac40019042f (diff)
parent6ded0f6763c776e42d363f2b5714c79a34c9b70f (diff)
downloadweb-7c90e65e25f673a9c621c6102ee3d7c130160b01.tar.gz
web-7c90e65e25f673a9c621c6102ee3d7c130160b01.tar.bz2
web-7c90e65e25f673a9c621c6102ee3d7c130160b01.zip
Merge commit '6ded0f6763c776e42d363f2b5714c79a34c9b70f'
Polish and enhance some pages some more.
Diffstat (limited to 'faq/support/0-drivers.mdwn')
-rw-r--r--faq/support/0-drivers.mdwn8
1 files changed, 7 insertions, 1 deletions
diff --git a/faq/support/0-drivers.mdwn b/faq/support/0-drivers.mdwn
index 974fb612..54b2d744 100644
--- a/faq/support/0-drivers.mdwn
+++ b/faq/support/0-drivers.mdwn
@@ -15,4 +15,10 @@ 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.
+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.