Support for MVME141 boards. Tested with both VME and VSB memory boards

(and MVME327 SCSI and MVME376 Ethernet, to provide a complete system).

2 files changed, 30 insertions, 10 deletions

diff --git a/distrib/notes/mvme68k/hardware b/distrib/notes/mvme68k/hardware
index 3f3f5a7e8b6..bf0b410edc9 100644
--- a/distrib/notes/mvme68k/hardware
+++ b/distrib/notes/mvme68k/hardware
@@ -1,8 +1,9 @@
-dnl	$OpenBSD: hardware,v 1.18 2009/03/01 21:40:48 miod Exp $
+dnl	$OpenBSD: hardware,v 1.19 2009/03/01 22:08:10 miod Exp $
 OpenBSD/MACHINE OSREV runs on the following classes of machines:
-	- MVME147 - Motorola with 68030 and 68881
+	- MVM:141 - Motorola with 68030 and 68882, with VSB interface
+	- MVME147 - Motorola with 68030 and 68882
 	- MVME162 - Motorola with 68040 and IndustryPack slots
-	- MVME165 - Motorola with 68040 and VSB interface
+	- MVME165 - Motorola with 68040, with VSB interface
 	- MVME167 - Motorola with 68040
 dnl 172 support is not tested
 	- MVME172 - Motorola with 68060 and IndustryPack slots
@@ -15,6 +16,14 @@ getting more RAM is more important than getting a faster CPU board.
 
 Supported devices {:-include-:}:
 
+MVME141:
+	memory:
+		both VME and VSB boards are supported, such as MVME224 boards
+	serial ports:
+		on-board ttyd0-ttyd1 - MC68681 (dart)
+	VMEbus:
+		supported
+
 MVME147:
 	serial ports:
 		on-board ttya-ttyd (zs)
diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install
index d228fc06dee..4af1f991f3d 100644
--- a/distrib/notes/mvme68k/install
+++ b/distrib/notes/mvme68k/install
@@ -1,4 +1,4 @@
-dnl	$OpenBSD: install,v 1.32 2009/02/17 22:37:43 miod Exp $
+dnl	$OpenBSD: install,v 1.33 2009/03/01 22:08:10 miod Exp $
 OpenBSDInstallPrelude
 
 There are several ways to install OpenBSD onto a disk. The easiest way
@@ -40,7 +40,7 @@ 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.
 
-Recent BUG can list the available disk and tape controllers, using the
+Most BUG versions can list the available disk and tape controllers, using the
 "IOT;H" command:
 
     167-Bug>IOT;H
@@ -65,9 +65,19 @@ the built-in SCSI controller (if present), using the following convention:
 - 'xx' is the device ID.
 - 'yy' is zero.
 
+MVME141 boards are quite similar to the MVME147, but can boot from various
+controller; the IOT;H command will list all the available boot options.
+Usually, the boot device numbers will be:
+- `xx' is the `Lun' value printed by IOT;H, and is usually the device ID.
+- `yy' is the subdevice number, if any.
+
+Thus to boot a MVME141 from a MVME327 controller:
+- `xx' is the SCSI device ID.
+- `yy' is zero.
+
 For example, booting from a tape drive using SCSI ID #4:
     147-Bug> BO 04 00
-for a MVME147, and
+for MVME141 and MVME147, and
     167-Bug> BO 00 40
 for any other MACHINE board using the built-in controller. However, a tape
 drive connected to an MVME328 board using SCSI ID #5, will be booted as:
@@ -119,9 +129,9 @@ controller will be reported:
     CLUN  DLUN  Name      Address
        0     0  VME167    $FFF46000
 
-If the BUG does not support the NIOT command (most MVME147 don't), then
-it has no support for netbooting, and you'll have to use S-Records,
-described later in this document.
+If the BUG does not support the NIOT command (most MVME141, MVME147
+and MVME165 don't), then it has no support for netbooting, and you'll
+have to use S-Records, described later in this document.
 
 Before netbooting, enter "NIOT" and fill the parameters. Be sure to provide
 the correct values for Controller LUN and Device LUN (as listed in the
@@ -190,7 +200,8 @@ where, in this example, 192.168.0.68 is the address of the MACHINE computer,
 and 192.168.0.1 the address of the diskless server.
 
 If the BUG version does not understand the NIOT and NBO commands (most
-MVME147 don't), the alternative is to boot from S-Records.
+MVME141, MVME147 and MVME165 don't), the alternative is to boot from
+S-Records.
 
 
 Booting from S-Records: