Subject: Converted vax docs
To: None <netbsd-docs@netbsd.org>
From: None <dsieger@techfak.uni-bielefeld.de>
List: netbsd-docs
Date: 04/04/2007 16:51:52
--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Hi,
attached are converted versions of
htdocs/Documentation/Hardware/Machines/DEC/vax/{bootrom,tk50}.list
and an according patch.
Regards,
Daniel
--
Daniel Sieger
Faculty of Technology
Bielefeld University
wwwhomes.uni-bielefeld.de/dsieger
--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="bootrom.xml"
<?xml version="1.0"?>
<!DOCTYPE webpage
PUBLIC "-//NetBSD//DTD Website-based NetBSD Extension//EN"
"http://www.NetBSD.org/XML/htdocs/lang/share/xml/website-netbsd.dtd">
<webpage id="Documentation-Hardware-Machines-DEC-vax-bootrom">
<config param="desc" value="VAX hardware reference"/>
<config param="cvstag" value="$NetBSD: $"/>
<config param="rcsdate" value="$Date: $"/>
<head>
<!-- Copyright (c) 1998-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED. -->
<title>Hardware Documentation - Machines DEC - VAX hardware
reference - Bootrom details</title>
</head>
<sect1 role="toc">
<sect2 id="bootrom">
<title>Bootrom details</title>
<sect3 id="boot">
<title>Boot options</title>
<para>Most ports pass options as single character flags (such
as '-a'). The VAX port uses bitflags directly. The full
list as of &os; 1.4 is given below, taken from
<filename>/usr/src/sys/sys/reboot.h</filename> (not all
flags make sense from the boot rom).</para>
<para>To use, boot with <command>b/</command> followed by the
flags you want (in hex). For example, to boot single user
and prompt for the kernel filename use</para>
<programlisting>
b/3</programlisting>
<table border="1">
<tr>
<th>Symbolic name</th>
<th>Value</th>
<th>Action</th>
</tr>
<tr>
<td>RB_ASKNAME</td>
<td> 0x001</td>
<td>ask for file name from which to reboot</td>
</tr>
<tr>
<td>RB_SINGLE</td>
<td> 0x002</td>
<td>reboot to single user only</td>
</tr>
<tr>
<td>RB_NOSYNC</td>
<td> 0x004</td>
<td>dont sync before reboot</td>
</tr>
<tr>
<td>RB_HALT</td>
<td> 0x008</td>
<td>don't reboot, just halt</td>
</tr>
<tr>
<td>RB_INITNAME</td>
<td> 0x010</td>
<td>name given for /etc/init (unused)</td>
</tr>
<tr>
<td>RB_DFLTROOT</td>
<td> 0x020</td>
<td>use compiled-in rootdev</td>
</tr>
<tr>
<td>RB_KDB</td>
<td> 0x040</td>
<td>give control to kernel debugger</td>
</tr>
<tr>
<td>RB_RDONLY</td>
<td> 0x080</td>
<td>mount root fs read-only</td>
</tr>
<tr>
<td>RB_DUMP</td>
<td> 0x100</td>
<td>dump kernel memory before reboot</td>
</tr>
<tr>
<td>RB_MINIROOT</td>
<td> 0x200</td>
<td>mini-root present in memory at boot time</td>
</tr>
<tr>
<td>RB_STRING</td>
<td> 0x400</td>
<td>use provided bootstr</td>
</tr>
<tr>
<td>RB_POWERDOWN</td>
<td> (RB_HALT|0x800)</td>
<td>turn power off (or at least halt)</td>
</tr>
</table>
</sect3>
<sect3 id="vs2000-test">
<title>MicroVAX 2000/VAXstation 2000 TEST commands</title>
<para>Commands to be typed at the boot monitor.</para>
<para><code>TEST</code> can be abbreviated to
<code>T</code>.</para>
<itemizedlist>
<listitem>
<para><code>TEST 0</code></para>
<para>Invokes the customer runnable system
excerciser. This test executes a serial string test of
all devices in the system. After serial device testing
has completed, a concurrent device test is executed.
The test automatically configures the test based on the
system's hardware configuration and will test all
devices present. This test runs for two test passes and
concludes with a summary table of test results.</para>
</listitem>
<listitem>
<para><code>TEST 50</code></para>
<para>Display the hardware configuration of the system.
Lists all functionality present along with status of
each device on the last diagnostic executed.
Additionally, this display identifies the current
revision of firmware in the system as well as the system
I.D. number (used as the system's hardware address when
networked).</para>
<para>Returned information:</para>
<table border="1">
<tr>
<th>Message</th>
<th align="left">Meaning</th>
</tr>
<tr>
<td align="right" valign="top">ID 08-00-2B-xx-yy-zz</td>
<td>Ethernet address</td>
</tr>
<tr>
<td align="right" valign="top">?? MONO 0001.F002</td>
<td>Base (mono) video option, only VAXstation.</td>
</tr>
<tr>
<td align="right" valign="top">? CLK 0000.0005</td>
<td>Clock battery is drained. Leave the box running, or change.</td>
</tr>
<tr>
<td align="right" valign="top">CLK 0000.0001</td>
<td>Clock battery OK.</td>
</tr>
<tr>
<td align="right" valign="top">NVR 0000.0001</td>
<td>Non-Volatile Read-only memory OK.</td>
</tr>
<tr>
<td align="right" valign="top">? DZ 0000.4001</td>
<td>00004001 00000001 00000001 00000001 00000000
00000000
<para>The above six eight-digit numbers refer to the
4 serial lines, the keyboard, and the mouse or
tablet. A MicroVAX 2000 should always show
00000000 00000000 as the last two numbers.</para>
</td>
</tr>
<tr>
<td align="right" valign="top">MEM 00xx.0001</td>
<td>0xx00000
<para>The .0001 means that the MEMory is healthy,
the 00xx, and the 0xx00000 both tell you the box
has xx MB of memory (in hex). If the first line,
second half is not .0001, there will be a second
eight digit number on the second line telling you
the details of the memory fault.</para>
</td>
</tr>
<tr>
<td align="right" valign="top">MM 0000.0001</td>
<td>Memory management</td>
</tr>
<tr>
<td align="right" valign="top">FP 0000.0001</td>
<td>Floating Point</td>
</tr>
<tr>
<td align="right" valign="top">IT 0000.0001</td>
<td>Interval Timer</td>
</tr>
<tr>
<td align="right" valign="top">HDC 7770.0001</td>
<td>00000000 00000000 00000000
<para>The Hard Disk Controller is healthy, but it
can't see any disks. Where it does see disks, the
second line shows their size (in Hex) in order
DUA0,DUA1,DUA2 RD32's=40Mb or 146B8, RD53's=71Mb
or 22000, RD54's=159Mb or 4C437. RX33's are either
1200KB or 960, or if using RX50's, 400KB or
320.</para>
</td>
</tr>
<tr>
<td align="right" valign="top">TPC 0202.0001</td>
<td>FFFFFF03 01000001 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05 FFFFFF05
FFFFFF05
<para>the tape-drive port is healthy and it sees a
good TK50-Z drive.</para>
</td>
</tr>
<tr>
<td align="right" valign="top">SYS 0000.0001</td>
<td>Main system test OK</td>
</tr>
<tr>
<td align="right" valign="top">8PLN 0000.0001</td>
<td>V1.4
<para>Healthy 8-plane graphics card, and Vx.x shows
its version number. Could alternatively be 4PLN
for the 4-plane card.</para>
</td>
</tr>
<tr>
<td align="right" valign="top">NI 0000.0001 V1.3</td>
<td>Healthy ethernet card found, with its version
number. There must be a terminator, or a terminated
ethernet for the card to test OK.</td>
</tr>
</table>
</listitem>
<listitem>
<para><code>TEST 51</code></para>
<para>Set default Boot device in NVR. Displays current
setting, then prompts for new value. Valid choices may
be DUA0,DUA1,DUA2 (Disks, where available), MUA0 (Tape)
or ESA0 (Ethernet). Enter a single . for no
default.</para>
</listitem>
<listitem>
<para><code>TEST 52</code></para>
<para>Sets the default Boot flags in NVR.</para>
</listitem>
<listitem>
<para><code>TEST 53</code></para>
<para>Sets the NVR default recovery action flags, used by
the system during power up and also used by the system
if an error is detected with the operating
environment.</para>
</listitem>
<listitem>
<para><code>TEST 54</code></para>
<para>Displays a language inquiry menu on the console
device (VAXstation 2000 only) to allow the customer to
select the appropriate keyboard type based on the
country keyboard in use. On MicroVAX 2000, this
function is accomplished through the language set-up
utility that is part of the console terminal. Set in
NVR.</para>
</listitem>
<listitem>
<para><code>TEST 61</code></para>
<para>Sends a full screen of E's to the console monitor
display (VAXstation 2000 only) allowing a quick check of
the monitor's linearity adjustments.</para>
</listitem>
<listitem>
<para><code>TEST 62</code></para>
<para>Sends a full white screen to the console monitor
display (VAXstation 2000 only) allowing a quick check of
the monitor's raster as well as a check of the video
controller's display memory.</para>
</listitem>
<listitem>
<para><code>TEST 70</code></para>
<para>Allows the customer to format hard disk drives and
RX33 floppy diskettes. RX50 diskettes need not use this
utility as they come pre-formatted. If formatting a
non-Digital Equipment Corporation hard disk drive, this
utility goes into a query mode thus allowing the
customer to enter drive parameter data prior to actually
performing the format operation.</para>
<para><emphasis role="bold">Note: Formatting destroys
all user data on the disk or diskette being
formatted.</emphasis></para>
<para>The set of parameters for an RD32 (aka Seagate
ST251) would be:</para>
<table border="1">
<tr>
<td><code>xbnsiz :=54</code></td>
<td>number of transfer blocks</td>
</tr>
<tr>
<td><code>dbnsiz :=48</code></td>
<td>number of diagnostic blocks</td>
</tr>
<tr>
<td><code>lbnsiz :=83236</code></td>
<td>number of logical blocks</td>
</tr>
<tr>
<td><code>rbnsiz :=200</code></td>
<td>number of replacement blocks</td>
</tr>
<tr>
<td><code>surpun :=6</code></td>
<td>number of surfaces per unit</td>
</tr>
<tr>
<td><code>cylpun :=820</code></td>
<td>number of cylinders per unit</td>
</tr>
<tr>
<td><code>wrtprc :=820</code></td>
<td>write precompensation cylinder</td>
</tr>
<tr>
<td><code>rctsiz :=4</code></td>
<td>size of the revectoring control table</td>
</tr>
<tr>
<td><code>rctnbr :=8</code></td>
<td>number of copies of the RCT</td>
</tr>
<tr>
<td><code>secitl :=1</code></td>
<td>sector interleave</td>
</tr>
<tr>
<td><code>stsskw :=2</code></td>
<td>surface to surface skew</td>
</tr>
<tr>
<td><code>ctcskw :=9</code></td>
<td>cylinder to cylinder skew</td>
</tr>
<tr>
<td><code>mediai :=627327008</code></td>
<td><ulink url="#mscp_media_ids">MSCP media ID</ulink></td>
</tr>
</table>
<para>The total disk size is the number of cylinders
(<code>cylpun</code>) times the number of surfaces
(<code>surpun</code>) times the number of sectors per
track (17). Then, this is believed to be used as
follows:</para>
<itemizedlist>
<listitem>The number of transfer blocks
(<code>xbnsiz</code> is always 54.</listitem>
<listitem>The number of diagnostic blocks
(<code>dbnsiz</code> should be calculated so that
<code>xbnsiz</code> + <code>dbnsiz</code> = one whole
cylinder.</listitem>
<listitem>The number of logical blocks
(<code>lbnsiz</code> includes the revectoring
table. With 8 copies of a 4 block table, this means
that the visible number of blocks for the OS is
<code>lbnsiz</code> - 32, and <code>lbnsiz</code> is
calculated as physical size - <code>xbnsiz</code> -
<code>dbnsiz</code> - <code>rbnsiz</code>.</listitem>
<listitem>The transfer blocks, diagnostic blocks and
revectoring table are allocated outside the logical
block area, so <code>lbnsiz</code> = physical size of
disk - <code>xbnsiz</code> - <code>dbnsiz</code> -
(<code>rctsiz</code> * <code>rctnbr</code>.</listitem>
</itemizedlist>
<para id="mscp_media_ids">Some known MSCP media IDs</para>
<table border="1">
<tr>
<th>ESE20</th><td>625685140</td>
<th>RA90</th><td>627314778</td>
<th>RD53</th><td>627327029</td>
<th>RFH73</th><td>577004617</td>
</tr>
<tr>
<th>ESE25</th><td>625685145</td>
<th>RA92</th><td>627314780</td>
<th>RD54</th><td>627327030</td>
<th>RRD40</th><td>627384872</td>
</tr>
<tr>
<th>RA60</th><td>581177404</td>
<th>RC25</th><td>543436825</td>
<th>RF30</th><td>577003550</td>
<th>RRD50</th><td>627384882</td>
</tr>
<tr>
<th>RA70</th><td>627314758</td>
<th>RC25F</th><td>543437593</td>
<th>RF31</th><td>577003551</td>
<th>RX18</th><td>627408914</td>
</tr>
<tr>
<th>RA71</th><td>627314759</td>
<th>RD31</th><td>627327007</td>
<th>RF71</th><td>577003591</td>
<th>RX33</th><td>627408929</td>
</tr>
<tr>
<th>RA72</th><td>627314760</td>
<th>RD32</th><td>627327008</td>
<th>RF72</th><td>577003592</td>
<th>RX35</th><td>627408931</td>
</tr>
<tr>
<th>RA80</th><td>627314768</td>
<th>RD33</th><td>627327009</td>
<th>RF73</th><td>577003593</td>
<th>RX50</th><td>627408946</td>
</tr>
<tr>
<th>RA81</th><td>627314769</td>
<th>RD51</th><td>627327027</td>
<th>RFH31</th><td>577004575</td>
<th>SVS00</th><td>560425344</td>
</tr>
<tr>
<th>RA82</th><td>627314770</td>
<th>RD52</th><td>627327028</td>
<th>RFH72</th><td>577004616</td>
</tr>
</table>
</listitem>
<listitem>
<para><code>TEST 71</code></para>
<para>A disk verifier utility. This utility does a
non-destructive test of hard disk formats to search for
new bad blocks on the media since operating system
installation and identifies any new bad blocks to the
customer. This utility is for use with hard disks
only.</para>
</listitem>
<listitem>
<para><code>TEST 90</code></para>
<para>A utility that is used with systems that are
connected in a network configuration. This utility, when
invoked, puts the system in a test mode to provide
loopback and system I.D. support to network level
diagnostics run from a host or boot node. Working in
combination with network level excercisers, this utility
assists in verifying the system's network
hardware/firmware interface is correctly
functioning.</para>
</listitem>
<listitem>
<para><code>TEST 80000050</code></para>
<para>A utility that displays all system firmware revision
levels by function (i.e. self test, bootstrap code,
console code, etc.).</para>
</listitem>
</itemizedlist>
</sect3>
<sect3 id="extended_diagnostics">
<title>Extended Diagnostics/Maintenance Utilities</title>
<para>This series of routines require the use of a special
hardware key to invoke and execute.</para>
<itemizedlist>
<listitem>
<para><code>TEST 60</code></para>
<para>A utility that displays a circle/crosshatch pattern
on the console monitor (VAXstation 2000 only). It is used
by service personnel to check/adjust monitor linearity
and aspect ratio.</para>
</listitem>
<listitem>
<para><code>TEST 72</code></para>
<para>A utility that writes a special key on scratch floppy
diskettes. After running a floppy diskette through this
utility, the diskette can then be used with the Field
Service system excerciser to do write testing of the
floppy diskette subsystem. Floppy diskettes used with
the system excerciser that do not have this special key
written on the media will do a read test only.</para>
</listitem>
<listitem>
<para><code>TEST 73</code></para>
<para>A utility that writes a special key on a scratch TK50
COMPACTape. After running the COMPACTape through this
utility, the cartridge can then be used with the Field
Service system excerciser to do write testing of the TK50
subsystem. Cartridges used with the system excerciser
that do not have this special key written on the media
will do a read test only.</para>
</listitem>
<listitem>
<para><code>TEST 101</code></para>
<para>Executes the Field Service mode system
excerciser. This test excercises each device once
sequentially and then excercises all devices
concurrently. This sequence is executed for two complete
passes of all system devices present in the
configuration. Loopback connectors and test media are
required to optimize test coverage with this
routine. This test automatically stops after two complete
passes and displays a test summary.</para>
</listitem>
<listitem>
<para><code>TEST 102</code></para>
<para>Executes the Field Service mode system excerciser. It
excercises all devices in the system configuration in the
same sequence as described for Test 101. However, when
Test 102 is invoked, the sequence is repeated
continuously until the user types
<command>CONTROL/C</command> at the system console. When
<command>CONTROL/C</command> is typed, the test
terminates at the conclusion of the current test pass and
displays a test summary. Note that the user must allow
this test to run for at least two complete passes before
typing <command>CONTROL/C</command>.</para>
</listitem>
<listitem>
<para><code>TEST 80000106</code></para>
<para>Allows the Field Service Engineer to select
individual device tests from the total test used in Test
102 described above. Whichever device tests are enabled
and executed run in a continuous loop until
<command>CONTROL/C</command> is typed at the system
console. As with Test 102, the user must allow this test
run for at least two complete passes before typing
<command>CONTROL/C</command>.</para>
</listitem>
</itemizedlist>
</sect3>
<sect3 id="vs2000-messages">
<title>MicroVAX 2000/VAXstation 2000 boot messages</title>
<para>The initial message will be something of the form:</para>
<programlisting>
KA410-A V1.2
F_..E...D...C...B...A...9...8...7...6...5...4_..3_..2_..1_..</programlisting>
<para>KA410-A will be displayed with the switch in multi-user
MicroVAX 2000 mode, KA410-B if set to single user VAXstation
2000. V1.2 is the ROM rev level (or 4- or 8-plane colour
graphics board, V2.1 is required). In the count-down a
<quote>_</quote> means the item wasn't found.</para>
<table border="1">
<tr>
<th>Message</th>
<th align="left">Error</th>
</tr>
<tr>
<td>? E 0040 0000.0005</td>
<td>clock battery needs charged</td>
</tr>
<tr>
<td>? C 0080 0000.4001</td>
<td>odd-ball terminal as console - should still work</td>
</tr>
</table>
<para>See also <ulink url="#vs2000-test">MicroVAX
2000/VAXstation 2000 TEST commands</ulink>.</para>
</sect3>
<sect3 id="vs3100">
<title>VAXstation 3100 Model 40 Power-Up and Self-Test Device
Identifiers</title>
<table border="1">
<tr>
<th>Identifier</th><th align="left">Device</th>
</tr>
<tr>
<td>F</td><td>Base video</td>
</tr>
<tr>
<td>E</td><td>System clock</td>
</tr>
<tr>
<td>D</td><td>Nonvolatile RAM</td>
</tr>
<tr>
<td>C</td><td>Serial line controller</td>
</tr>
<tr>
<td>B</td><td>Memory</td>
</tr>
<tr>
<td>A</td><td>Memory-management unit</td>
</tr>
<tr>
<td>9</td><td>Floating point unit</td>
</tr>
<tr>
<td>8</td><td>Interval timer</td>
</tr>
<tr>
<td>7</td><td>Disk controller option</td>
</tr>
<tr>
<td>6</td><td>Disk controller option</td>
</tr>
<tr>
<td>5</td><td>Interrupt controller and Ethernet ID
ROM</td>
</tr>
<tr>
<td>4</td><td>Optional 8-plane graphics coprocessor</td>
</tr>
<tr>
<td>3</td><td>Reserved for later use</td>
</tr>
<tr>
<td>2</td><td>Reserved for later use</td>
</tr>
<tr>
<td>1</td><td>Ethernet network interconnect (NI)</td>
</tr>
</table>
</sect3>
</sect2>
</sect1>
<parentsec url="./" text="VAX hardware reference"/>
</webpage>
--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="tk50.xml"
<?xml version="1.0"?>
<!DOCTYPE webpage
PUBLIC "-//NetBSD//DTD Website-based NetBSD Extension//EN"
"http://www.NetBSD.org/XML/htdocs/lang/share/xml/website-netbsd.dtd">
<webpage id="Documentation-Hardware-Machines-DEC-vax-bootrom">
<config param="desc" value="VAX hardware reference"/>
<config param="cvstag" value="$NetBSD: $"/>
<config param="rcsdate" value="$Date: $"/>
<head>
<!-- Copyright (c) 1998-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED. -->
<title>Hardware Documentation - Machines DEC - VAX hardware
reference - TK50/TK70 FAQ</title>
</head>
<sect1 role="toc">
<sect2 id="gems">
<title>Top 4 gems of TK50/TK70 wisdom</title>
<sect3 id="difference">
<title>What is the difference between a TK50 and
TK70</title>
<itemizedlist>
<listitem>
<para>A TK50 drive works on TQK50 or TQK70 controller,
writes/reads TK50 tapes (known as CompacTape). If
you can choose between a TQK50 or TQK70 controller
for the TK50 drive, take the TQK70. It's
faster.</para>
</listitem>
<listitem>
<para>A TK70 drive works on a TQK70 controller,
writes/reads TK70 tapes (known as CompacTape II),
and can read TK50 tapes (not write).</para>
</listitem>
</itemizedlist>
</sect3>
<sect3 id="cleaning">
<title>How to clean a TK50/TK70 drive</title>
<para>TK50/TK70 drives are better dust/dirt magnets than
most of the vacuum cleaners in the known universe. Most
of the problems you with a TK50/TK70 are due to
dirt/dust on the tacho/LEDs inside the drive.</para>
<para>If the drive is dirty, open the metal cover (nothing
more), and clean it carefully. In particular clean the 4
LEDs and the area immediately around. Since you already
have the drive open check the <quote>Take Up
Leader</quote> (used to feed the tape) is not bent or
broken. If you have to replace it, the DEC-PART-NUMBER
is 74-28268.</para>
</sect3>
<sect3 id="erasing-tapes">
<title>How to erase TK50/TK70 tapes</title>
<para>What you need for erasing a tape:</para>
<itemizedlist>
<listitem>A $1000 bulk eraser, or</listitem>
<listitem>a $0.20 magnet.</listitem>
</itemizedlist>
<para>If you can operate your drive outside the computer,
remove the metal cover of the drive, and put the magnet
near the tape while the drive try to feed the tape
in.</para>
<para><emphasis role="bold">DO NOT PUT THE MAGNET NEAR TO
THE READ/WRITE HEAD OF THE DRIVE !!!</emphasis></para>
<para>This procedure is not without risk, and we accept no
responsibility for non functional drives!</para>
<para>If you can't operate the drive open, use the bulk
eraser ;-)</para>
</sect3>
<sect3 id="tk50-as-tk70">
<title>Can you reformat TK50 tapes as TK70s</title>
<para>Once you <ulink url="#erasing-tapes">erase</ulink> a
TK50 you can use it in a TK70 drive and vice versa, but
the TK50 and TK70 tape material is different, and the
write current of the TK70 drive is different
(lower). This is <emphasis>not</emphasis> recommended,
and should be used for temporary storage for which you
will suffer no pain if lost.</para>
</sect3>
</sect2>
</sect1>
<parentsec url="./" text="VAX hardware reference"/>
</webpage>
--RnlQjJ0d97Da+TV1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="vax.diff"
Index: layout.xml
===================================================================
RCS file: /cvsroot/htdocs/layout.xml,v
retrieving revision 1.231
diff -u -r1.231 layout.xml
--- layout.xml 4 Apr 2007 08:21:51 -0000 1.231
+++ layout.xml 4 Apr 2007 14:32:29 -0000
@@ -56,6 +56,8 @@
<tocentry page="Documentation/Hardware/Machines/DEC/vax/othervaxes.xml" filename="othervaxes.html"/>
<tocentry page="Documentation/Hardware/Machines/DEC/vax/storage.xml" filename="storage.html"/>
<tocentry page="Documentation/Hardware/Machines/DEC/vax/cards.xml" filename="cards.html"/>
+ <tocentry page="Documentation/Hardware/Machines/DEC/vax/bootrom.xml" filename="bootrom.html"/>
+ <tocentry page="Documentation/Hardware/Machines/DEC/vax/tk50.xml" filename="tk50.html"/>
<tocentry page="Documentation/Hardware/Machines/DEC/vax/busses.xml" filename="busses.html"/>
<tocentry page="Documentation/Hardware/Machines/DEC/vax/monitors.xml" filename="monitors.html"/>
<tocentry page="Documentation/Hardware/Machines/DEC/vax/enclosures.xml" filename="enclosures.html"/>
Index: Makefile
===================================================================
RCS file: /cvsroot/htdocs/Documentation/Hardware/Machines/DEC/vax/Makefile,v
retrieving revision 1.9
diff -u -r1.9 Makefile
--- Makefile 29 Jul 2006 11:58:33 -0000 1.9
+++ Makefile 4 Apr 2007 14:33:12 -0000
@@ -1,7 +1,7 @@
# $NetBSD: Makefile,v 1.9 2006/07/29 11:58:33 rillig Exp $
-LISTDOCS= bootrom.list tk50.list
-
+XMLDOCS+= tk50
+XMLDOCS+= bootrom
XMLDOCS+= busses
XMLDOCS+= cards
XMLDOCS+= enclosures
--RnlQjJ0d97Da+TV1--