[src/trunk]: src/distrib/notes/mvme68k Mention support for mvme172 and mvme17...

[scw <scw%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/5b5ec140bf95
branches:  trunk
changeset: 499510:5b5ec140bf95
user:      scw <scw%NetBSD.org@localhost>
date:      Tue Nov 21 12:38:59 2000 +0000

description:
Mention support for mvme172 and mvme177 in all the relevant places.

diffstat:

 distrib/notes/mvme68k/hardware |  21 +++++++++++++--------
 distrib/notes/mvme68k/install  |  20 ++++++++++----------
 distrib/notes/mvme68k/prep     |  35 +++++++++++++++++++++++++----------
 distrib/notes/mvme68k/xfer     |  11 ++++++++---
 4 files changed, 56 insertions(+), 31 deletions(-)

diffs (236 lines):

diff -r 3aca8d946fed -r 5b5ec140bf95 distrib/notes/mvme68k/hardware
--- a/distrib/notes/mvme68k/hardware    Tue Nov 21 12:28:15 2000 +0000
+++ b/distrib/notes/mvme68k/hardware    Tue Nov 21 12:38:59 2000 +0000
@@ -1,12 +1,17 @@
-.\"    $NetBSD: hardware,v 1.7 2000/11/01 10:58:29 scw Exp $
+.\"    $NetBSD: hardware,v 1.8 2000/11/21 12:38:59 scw Exp $
 .
 .Nx*M
 \*V runs on Motorola
 .Tn MVME147
 ,
-.Tn MVME162-LX
+.Tn MVME162
+,
+.Tn MVME167
+,
+.Tn MVME172
+,
 and
-.Tn MVME167
+.Tn MVME177
 Single Board Computers.
 .Pp
 The minimal configuration requires 8 MB of RAM and ~200 MB of disk space.
@@ -82,17 +87,17 @@
 .bullet)
 .bullet)
 .
-.Ss2 Supported VME162-LX hardware
+.Ss2 Supported VME162/VME172 hardware
 .(bullet -offset indent
 Serial ports (RS232)
 .(bullet -compact
 built-in console
 .It
-ttyZ1
+ttyC1
 .It
-ttyZ2
+ttyC2
 .It
-ttyZ3
+ttyC3
 .bullet)
 .It
 Network interfaces:
@@ -117,7 +122,7 @@
 .bullet)
 .bullet)
 .
-.Ss2 Supported VME167 hardware
+.Ss2 Supported VME167/VME177 hardware
 .(bullet -offset indent
 Serial ports (RS232)
 .(bullet -compact
diff -r 3aca8d946fed -r 5b5ec140bf95 distrib/notes/mvme68k/install
--- a/distrib/notes/mvme68k/install     Tue Nov 21 12:28:15 2000 +0000
+++ b/distrib/notes/mvme68k/install     Tue Nov 21 12:38:59 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: install,v 1.11 2000/11/01 10:58:29 scw Exp $
+.\"    $NetBSD: install,v 1.12 2000/11/21 12:38:59 scw Exp $
 .\"
 .\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -91,7 +91,7 @@
 Volume: NBSD
 
 IPL loaded at:  $003F0000
-\*>\*> BSD MVME147 tapeboot [$Revision: 1.11 $]
+\*>\*> BSD MVME147 tapeboot [$Revision: 1.12 $]
 578616+422344+55540+[46032+51284]=0x11a6e4
 Start @ 0x8000 ...
 Copyright (c) 1996, 1997, 1998, 1999, 2000
@@ -386,7 +386,7 @@
 .Dl Cold/Warm Reset flag [C,W] = C?
 .Dl Execute Soft Reset [Y,N] N? Ic y
 .Pp
-Resetting the MVME162-LX and MVME167 boards are very similar.
+Resetting the other types of MVME boards are very similar.
 You should now reboot from that just installed miniroot. See the section
 entitled
 .Sx "Booting the miniroot"
@@ -469,22 +469,22 @@
 .Pp
 See below for the next step in booting MVME147.
 .Pp
-The MVME162-LX and MVME167 boards are able to download netboot
+The MVME162, MVME167, MVME172 and MVME177 boards are able to download netboot
 directly using TFTP.
 To enable this, you must first configure the networking parameters
 on the board as described in the section entitled "Preparing your System
 for
 .Nx
-Installation. On a properly configured MVME162-LX or MVME167, all you need
+Installation. On a properly configured MVME162/172 or MVME167/177, all you need
 to type is:
 .Pp
-.Dl 16x-Bug\*> Ic nbo
+.Dl 1xx-Bug\*> Ic nbo
 .Pp
 For all board types, the boot messages are very similar:
 .Pp
 .(disp
 Start @ 0x8000 ...
-\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.11 $]
+\*>\*> BSD MVME147 netboot (via sboot) [$Revision: 1.12 $]
 device: le0 attached to 08:00:3e:20:cb:87
 boot: client IP address: 192.168.1.4
 boot: client name: soapy
@@ -534,7 +534,7 @@
 .Pp
 .Dl ssh: Ic "ifconfig ie0 inet 192.168.1.4 up"
 .Pp
-will bring up the MVME162-LX or MVME167 network interface
+will bring up the MVME162/172 or MVME167/177 network interface
 .Li ie0
 with that address.
 The next
@@ -596,9 +596,9 @@
 .Pp
 .Dl 147-Bug\*> Ic "bo 0,,b:"
 .Pp
-The corresponding 162Bug or 167Bug boot command is:
+The corresponding 162Bug, 167Bug, 172Bug or 177Bug boot command is:
 .Pp
-.Dl 16x-Bug\*> Ic "bo 0,,,b:"
+.Dl 1xx-Bug\*> Ic "bo 0,,,b:"
 .Pp
 The command line parameters above are:
 .Pp
diff -r 3aca8d946fed -r 5b5ec140bf95 distrib/notes/mvme68k/prep
--- a/distrib/notes/mvme68k/prep        Tue Nov 21 12:28:15 2000 +0000
+++ b/distrib/notes/mvme68k/prep        Tue Nov 21 12:38:59 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: prep,v 1.9 2000/11/01 10:58:29 scw Exp $
+.\"    $NetBSD: prep,v 1.10 2000/11/21 12:39:00 scw Exp $
 .
 \*M machines usually need little or no preparation before installing
 .Nx ,
@@ -7,19 +7,34 @@
 on any attached storage devices.
 .Pp
 The exception to the above is that
-.Tn MVME162-LX
+.Tn MVME162
+,
+.Tn MVME167
+,
+.Tn MVME172
 and
-.Tn MVME167
-boards require a jumper to be removed before
+.Tn MVME177
+boards require a jumper to be removed or DIP switch changed before
 .Nx
 can be installed.
 On
 .Tn MVME162-LX
+and
+.Tn MVME172-LX
 pins 1-2 of jumper J11
 .Em must
 be removed.
 On
+.Tn MVME162-P2/P4
+and
+.Tn MVME172-P2/P4
+switch S4, position 8
+.Em must
+be set to OFF.
+On
 .Tn MVME167
+and
+.Tn MVME177
 pins 1-2 of jumper J1
 .Em must
 be removed.
@@ -38,8 +53,8 @@
 147-Bug\*>
 .disp)
 .Pp
-Or, if you have an MVME162-LX or MVME167 board (the following boot
-message is from MVME167; MVME162-LX is similar):
+Or, if you have an MVME162/172 or MVME167/177 board (the following boot
+message is from MVME167; the others are similar):
 .(disp
 MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94
 COLD Start
@@ -79,17 +94,17 @@
 Motorola has acknowledged a year 2000 bug in some versions of the MVME147
 whereby the day of the week
 doesn't get set correctly by the 147Bug PROM.
-.Em \It does not affect
+.Em It does not affect
 .Nx "" !
 .Pp
 Also make sure that your board's ethernet address is initialised to
 the correct value. You'll find the address on a label on the inside of
-the MVME147's front panel, and on the VMEbus P2 connector of the MVME162-LX
-and MVME167.
+the MVME147's front panel, and on the VMEbus P2 connector of the other
+board types.
 On the MVME147, enter the last five digits of the address
 using the
 .Ic lsad
-command. On the MVME162-LX and MVME167, you should use the
+command. On the MVME162/172 and MVME167/177, you should use the
 .Ic cnfg
 command.
 .Pp
diff -r 3aca8d946fed -r 5b5ec140bf95 distrib/notes/mvme68k/xfer
--- a/distrib/notes/mvme68k/xfer        Tue Nov 21 12:28:15 2000 +0000
+++ b/distrib/notes/mvme68k/xfer        Tue Nov 21 12:38:59 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: xfer,v 1.8 2000/11/01 10:58:29 scw Exp $
+.\"    $NetBSD: xfer,v 1.9 2000/11/21 12:39:00 scw Exp $
 .
 Installation is supported from several media types, including:
 .(bullet
@@ -108,9 +108,14 @@
 install directory of this distribution.
 .Pp
 The
-.Tn MVME162-LX
+.Tn MVME162
+,
+.Tn MVME167
+,
+.Tn MVME172
+,
 and
-.Tn MVME167
+.Tn MVME177
 boot ROMs have code builtin to boot over ethernet from a
 TFTP server. You should configure it to download the same
 .Pa netboot