diff options
| author | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-03-17 12:51:55 +0100 |
|---|---|---|
| committer | Samuel Thibault <samuel.thibault@ens-lyon.org> | 2013-03-17 12:51:55 +0100 |
| commit | 4c9c96e78f9967a9e23db38d45fbb4b58149488c (patch) | |
| tree | 76a4a6c4ce3e6b405b8e41bb768e4582a58ccfd1 | |
| parent | 306f359688afa254dc8728c73afab0fdb33d39ab (diff) | |
mention linux version
| -rw-r--r-- | faq/how_about_drivers.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/faq/how_about_drivers.mdwn b/faq/how_about_drivers.mdwn index 0e1887ba..974fb612 100644 --- a/faq/how_about_drivers.mdwn +++ b/faq/how_about_drivers.mdwn @@ -13,6 +13,6 @@ License|/fdl]]."]]"""]] 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 drivers in userland processes, +[[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. |