Mention MVME188 again.

3 files changed, 41 insertions, 25 deletions

diff --git a/distrib/notes/mvme88k/hardware b/distrib/notes/mvme88k/hardware
index 17a63ba04ce..0c826c9e6cf 100644
--- a/distrib/notes/mvme88k/hardware
+++ b/distrib/notes/mvme88k/hardware
@@ -1,30 +1,49 @@
-dnl	$OpenBSD: hardware,v 1.4 2003/09/06 23:34:01 miod Exp $
-OpenBSD/MACHINE OSREV runs on the following classes of machines:
-	- MVME187 - Single board computer with 88100 processor
-	- Motorola 8120 - non expandable MVME187
+dnl	$OpenBSD: hardware,v 1.5 2003/12/30 10:45:45 miod Exp $
+OpenBSD/MACHINE OSREV runs on the following MVME boards:
+
+	- MVME187 (Single board computer with 88100 processor)
+	- MVME188 (HYPERmodule-based systems with up to 4 88100 processors)
+
+OpenBSD/MACHINE OSREV also runs on the Motorola M8120 system, which is a
+non-expandable MVME187.
 
 The minimal configuration requires 16MB of RAM and ~250M of disk space.
 To install the entire system requires much more disk space, and to
 compile the system, more RAM is recommended.
 
+Supported HYPERmodules: (for MVME188 systems)
+	2P64 (2 88100 processors, 4 88200 CMMUs)
+	2P256 (2 88100 processors, 4 88204 CMMUs)
+	4P128 (4 88100 processors, 8 88200 CMMUs)
+	4P512 (4 88100 processors, 8 88204 CMMUs)
+
+The 1P64, 1P128, 2P128 and 2P512 HYPERmodules are not currently supported.
+
 Supported devices {:-include-:}:
 
-MVME187, Motorola 8120:
+MVME187:
 	serial ports:
-		on-board tty00 - tty03 - Cirrus Logic CD2401
+		on-board Cirrus Logic CD2401 tty00-tty03 (cl)
 	ethernet:
-		on-board Intel 82596CA ethernet ("ie0")
+		on-board Intel 82596CA ethernet (ie)
 	SCSI:
-		on-board SCSI controller NCR53c710
+		on-board SCSI controller NCR53c710 (ssh)
 	SRAM:
 		supported
 	VMEbus:
-		supported (on MVME187 only, the 8120 does not have VME)
+		supported
+
+MVME188:
+	serial ports:
+		on-board (SYSCON) serial ports ttya-ttyb (dart)
+	VMEbus:
+		supported
 
 Additional VMEbus devices supported by the OpenBSD/MACHINE port {:-include-:}:
 
-	MVME328 SCSI controller (vs)
+	MVME328 High Performance SCSI Controller (vs)
+
+	MVME332XT High Performance Serial I/O Controller (vx)
 
-	MVME332 Serial controller (vx)
+	MVME376 Ethernet Communications Controller (le)
 
-	MVME376 Ethernet controller (ve)
diff --git a/distrib/notes/mvme88k/install b/distrib/notes/mvme88k/install
index 091a60026c5..4395743bb4b 100644
--- a/distrib/notes/mvme88k/install
+++ b/distrib/notes/mvme88k/install
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: install,v 1.10 2003/09/06 23:34:01 miod Exp $
+dnl	$OpenBSD: install,v 1.11 2003/12/30 10:45:45 miod Exp $
 OpenBSDInstallPrelude
 
 There are several ways to install OpenBSD onto a disk. The easiest way
@@ -32,15 +32,13 @@ system is completely halted).
 
 Booting from SCSI tape:
 
-dnl XXX 188 does not have built-in devices - will need slight changes once
-dnl 188 support is back.
 Bootable tapes can be booted with the following command at the prompt:
 
     187-Bug> BO xx yy
 
 Where `xx' is the SCSI controller number (00 for the built-in SCSI
-controller), and `yy' is the encoding for the SCSI device ID, which varies
-between controllers.
+controller on MVME187), and `yy' is the encoding for the SCSI device ID,
+which varies between controllers.
 
 Recent BUG can list the available disk and tape controllers, using the
 "IOT;H" command:
@@ -55,7 +53,7 @@ In this example, the built-in controller, as well as an external MVME328
 controller, are available.
 
 The encoding for the drive ID is as follows:
-- built-in controller and MVME327 SCSI controller:
+- MVME187 built-in controller and MVME327 SCSI controller:
     'yy' is ten times the device ID.
 - MVME328 SCSI controller:
     'yy' is eight times the devic ID, written in hexadecimal
@@ -64,7 +62,7 @@ The encoding for the drive ID is as follows:
 
 For example, booting from a tape drive using SCSI ID #5 will be done with:
     187-Bug> BO 00 50
-using the built-in controller, but with:
+using the MVME187 built-in controller, but with:
     187-Bug> BO 06 28
 using an MVME328 board.
 
@@ -106,16 +104,15 @@ network controllers is available with the "NIOT;A" command. For example:
       15     0  VME374    $FF500000
 
 The "NIOT;H" lists only the available controllers in the machine. For
-example, if no external network card is present, only the built-in
-controller will be reported:
+example, on an MVME187 system with no external network card:
 
     187-Bug> NIOT;A
     Network Controllers/Nodes Available
     CLUN  DLUN  Name      Address
        0     0  VME187    $FFF46000
 
-If the BUG does not support the NIOT command (most MVME187 don't), then
-it has no support for netbooting.
+If the BUG does not support the NIOT command (MVME187 BUG prior to version
+1.3 doesn't), then it has no support for netbooting.
 
 Before netbooting, enter "NIOT" and fill the parametrs. Be sure to provide
 the correct values for Controller LUN and Device LUN (as listed in the
diff --git a/distrib/notes/mvme88k/whatis b/distrib/notes/mvme88k/whatis
index c8f4b8760f1..758133f4617 100644
--- a/distrib/notes/mvme88k/whatis
+++ b/distrib/notes/mvme88k/whatis
@@ -1,3 +1,3 @@
-dnl	$OpenBSD: whatis,v 1.3 2003/08/10 21:04:06 miod Exp $
-OpenBSD/MACHINE is an experimental port of OpenBSD to the Motorola 881x0
+dnl	$OpenBSD: whatis,v 1.4 2003/12/30 10:45:45 miod Exp $
+OpenBSD/MACHINE is a port of OpenBSD to the Motorola 881x0
 processor-based VME boards.