summaryrefslogtreecommitdiff
path: root/microkernel/mach/gnumach
diff options
context:
space:
mode:
authorSamuel Thibault <samuel.thibault@ens-lyon.org>2013-05-11 00:34:50 +0200
committerSamuel Thibault <samuel.thibault@ens-lyon.org>2013-05-11 00:34:50 +0200
commit4bfeb927ae2401b25c86843cc0c2d39462eef8ad (patch)
tree5db711826565b9ec7dd7ea5e85ff8e9a177940a9 /microkernel/mach/gnumach
parent19e8c3558e215189e9e5483ea0344bcac61a42dd (diff)
AHCI is here
Diffstat (limited to 'microkernel/mach/gnumach')
-rw-r--r--microkernel/mach/gnumach/hardware_compatibility_list.mdwn8
1 files changed, 4 insertions, 4 deletions
diff --git a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
index 3a4f560c..587178e9 100644
--- a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
+++ b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
@@ -71,17 +71,17 @@ e.g. drives with hundreds of GiB of storage space, see [[!GNU_Savannah_bug
## SATA
-SATA drives may work in compatibility mode.
+SATA drives can work in IDE compatibility mode or in AHCI mode.
This is how booting a [[GNU/Hurd_system|hurd]] will typically fail if GNU Mach
-couldn't connect to the hard disk, e.g., in a SATA system without IDE
+couldn't connect to the hard disk, e.g., in a SATA system without IDE or AHCI
compatibility mode:
start (hd0,3)/hurd/ext2fs.static: (hd0,3)/hurd/ext2fs.static
device:hd0s4: No such device or address
-There *may* be an option in the system's BIOS setup to configure enabling such
-a compatibility mode.
+There should be an option in the system's BIOS setup to configure enabling at
+least the AHCI compatibility mode.
# Device Drivers