Merge branch 'master' of flubber:~hurd-web/hurd-web

3 files changed, 38 insertions, 8 deletions

diff --git a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
index 2152c079..6c984784 100644
--- a/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
+++ b/microkernel/mach/gnumach/hardware_compatibility_list.mdwn
@@ -1,4 +1,4 @@
-[[!meta copyright="Copyright © 2007, 2008, 2009 Free Software Foundation,
+[[!meta copyright="Copyright © 2007, 2008, 2009, 2011 Free Software Foundation,
 Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
@@ -6,8 +6,8 @@ id="license" text="Permission is granted to copy, distribute and/or modify this
 document under the terms of the GNU Free Documentation License, Version 1.2 or
 any later version published by the Free Software Foundation; with no Invariant
 Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
-is included in the section entitled
-[[GNU Free Documentation License|/fdl]]."]]"""]]
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
 
 # CPU Architecture
 
@@ -68,10 +68,11 @@ All common IDE drives should work.  Some drive geometries do not work,
 e.g. drives with hundreds of GiB of storage space, see [[!GNU_Savannah_bug
 26425]].
 
-[[!toggle id="SATA" text="SATA drives may work in compatibility mode."]]
-<!-- Sure?  --[[tschwinge]] -->
 
-[[!toggleable id="SATA" text="""
+## SATA
+
+SATA drives may work in compatibility 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
 compatibility mode:
@@ -81,7 +82,7 @@ compatibility mode:
 
 There *may* be an option in the system's BIOS setup to configure enabling such
 a compatibility mode.
-"""]]
+
 
 # Device Drivers
 
diff --git a/microkernel/mach/gnumach/hardware_compatibility_list/discussion.mdwn b/microkernel/mach/gnumach/hardware_compatibility_list/discussion.mdwn
index 69ca3190..2b65956a 100644
--- a/microkernel/mach/gnumach/hardware_compatibility_list/discussion.mdwn
+++ b/microkernel/mach/gnumach/hardware_compatibility_list/discussion.mdwn
@@ -1,4 +1,33 @@
+[[!meta copyright="Copyright © 2007, 2008, 2011 Free Software Foundation,
+Inc."]]
+
+[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
+id="license" text="Permission is granted to copy, distribute and/or modify this
+document under the terms of the GNU Free Documentation License, Version 1.2 or
+any later version published by the Free Software Foundation; with no Invariant
+Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
+is included in the section entitled [[GNU Free Documentation
+License|/fdl]]."]]"""]]
+
+[[!tag open_issue_documentation]]
+
 Further information may still be found on
 <http://www.nongnu.org/thug/gnumach_hardware.html>
 and could perhaps be incorporated into that page.
 --[[tschwinge]]
+
+
+# SATA
+
+IRC, freenode, +hurd, 2011-07-24
+
+    <braunr> youpi: concerning the ide compatibility problem, it seems some
+      bioses provide several modes
+    <braunr> youpi: "legacy ide" and "native ide"
+    <braunr> i don't know what native ide really means, but when debugging ide
+      probing in gnumach, it just looks like there is nothing to detect
+    <braunr> and even in this mode, linux uses the ahci driver
+    <youpi> apparently native means it still uses the IDE protocol, but
+      possibly with other IRQs
+    <youpi> i.e. you need a PCI driver to handle that
+    <braunr> ok
diff --git a/microkernel/mach/port.mdwn b/microkernel/mach/port.mdwn
index ba2e22c2..7f02628d 100644
--- a/microkernel/mach/port.mdwn
+++ b/microkernel/mach/port.mdwn
@@ -49,7 +49,7 @@ send-once right.  These messages are (probably) queued and when the server task
 tries to receive messages by having a [[thread]] use its port receive right, it
 gets the message(s).  This is called [[IPC]].
 
-Port rights themselvse can be [[delegate]]d in a [[message]], too.  When the
+Port rights themselves can be [[delegate]]d in a [[message]], too.  When the
 receiver dequeues the message, the right is made available to it.
 
 The delivery of [[message]]s is reliable and strictly ordered.  When a