Mention MVME197

2 files changed, 13 insertions, 10 deletions

diff --git a/distrib/notes/mvme88k/hardware b/distrib/notes/mvme88k/hardware
index 51d68854321..9f39283496f 100644
--- a/distrib/notes/mvme88k/hardware
+++ b/distrib/notes/mvme88k/hardware
@@ -1,9 +1,11 @@
-dnl	$OpenBSD: hardware,v 1.10 2007/11/09 18:15:21 miod Exp $
+dnl	$OpenBSD: hardware,v 1.11 2007/12/15 21:28:07 miod Exp $
 OpenBSD/MACHINE OSREV runs on the systems built around the following
 MVME boards:
 
 	- MVME187 (Single board computer with 88100 processor)
 	- MVME188 (HYPERmodule-based systems with up to 4 88100 processors)
+	- MVME197LE (Single board computer with 88110 processor)
+	- MVME197SP/DP (Single board computer with up to two 88110 processors)
 
 Besides various Motorola complete systems (M8120, MVME187-based series
 900, etc), OpenBSD/MACHINE also runs on the MVME187-based Triton Dolphin
@@ -11,7 +13,8 @@ System 100.
 
 OpenBSD/MACHINE OSREV supports MVME188 SMP (Symmetrical MultiProcessor)
 systems.  To support SMP operation, a separate SMP kernel (bsd.mp)
-is included with the installation file sets.
+is included with the installation file sets. SMP is not yet supported on
+MVME197DP systems.
 
 The minimal configuration requires 16MB of RAM and ~250MB of disk space.
 To install the entire system requires much more disk space, and to
@@ -34,7 +37,7 @@ Supported HYPERmodules: (for MVME188 systems)
 
 Supported devices:
 
-MVME187 on-board devices:
+MVME187 and MVME197 on-board devices:
 	Cirrus Logic CD2401 serial ports, tty00-tty03/tty07(M8120) (cl)
 	Intel 82596CA Ethernet (ie)
 	NCR53c710 SCSI Controller (ssh)
diff --git a/distrib/notes/mvme88k/install b/distrib/notes/mvme88k/install
index a01b362e58a..53ce1e11937 100644
--- a/distrib/notes/mvme88k/install
+++ b/distrib/notes/mvme88k/install
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: install,v 1.20 2007/03/01 19:24:45 miod Exp $
+dnl	$OpenBSD: install,v 1.21 2007/12/15 21:28:07 miod Exp $
 OpenBSDInstallPrelude
 
 There are several ways to install OpenBSD onto a disk. The easiest way
@@ -49,8 +49,8 @@ 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 on MVME187), and `yy' is the encoding for the SCSI device ID,
-which varies between controllers.
+controller on MVME187 and MVME197), 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:
@@ -65,7 +65,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:
-- MVME187 built-in controller and MVME327 SCSI controller:
+- MVME187 and MVME197 built-in controller and MVME327 SCSI controller:
     'yy' is ten times the device ID.
 - MVME328 SCSI controller:
     'yy' is eight times the device ID, written in hexadecimal
@@ -89,9 +89,9 @@ are provided: one for Sun-compatible diskless setup (bootparams and NFS
 root), and a simpler version limited to TFTP support.
 
 The Sun-compatible network bootloader currently only supports the MVME187
-on-board interface, and will not be able to boot from any other Ethernet
-controller. The tftp bootloader does not have this limitation and will boot
-from any BUG-supported Ethernet controller.
+and MVME197 on-board interface, and will not be able to boot from any other
+Ethernet controller. The tftp bootloader does not have this limitation and
+will boot from any BUG-supported Ethernet controller.
 
 If you plan to use the Sun-compatible bootloader, "netboot", it will be
 necessary to set up a complete diskless client configuration on a server. If