diff options
| author | Thomas Schwinge <thomas@codesourcery.com> | 2013-05-14 22:08:50 +0200 |
|---|---|---|
| committer | Thomas Schwinge <thomas@codesourcery.com> | 2013-05-14 22:08:50 +0200 |
| commit | fb2826e358e561838f11416c071e62416d642fdf (patch) | |
| tree | aca00655ed4758cdc8f8d57e9a718ac8d244ad23 /faq/drivers.mdwn | |
| parent | fd294a621997fffb2593cd197836d0c6946a35b5 (diff) | |
| parent | f651dceb8874a277bd0da6d09f3448f1553b520d (diff) | |
Merge remote-tracking branch 'darnassus--hurd-web/master'
Diffstat (limited to 'faq/drivers.mdwn')
| -rw-r--r-- | faq/drivers.mdwn | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/faq/drivers.mdwn b/faq/drivers.mdwn index 197d47b7..57ed7ea9 100644 --- a/faq/drivers.mdwn +++ b/faq/drivers.mdwn @@ -17,8 +17,9 @@ 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. [[microkernel/mach/gnumach/ports/Xen]] is also supported, both blkfront -and netfront. +bugs. Firmware loading is however not implemented yet. +[[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 |