diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-05-04 12:11:28 +0200 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-05-04 12:11:28 +0200 |
| commit | 69244b8a4c65331b5e96702345fb006959d0025d (patch) | |
| tree | 0a2a549ad13c7ff68df4e53e5fac1a0d281386b3 /faq/drivers.mdwn | |
| parent | eb968777328077ca2c4b0818deb011926de729ad (diff) | |
Mention that firmware loading is not implemented
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 |