initial import of NetBSD tree

21 files changed, 3283 insertions, 0 deletions

diff --git a/share/man/man4/man4.hp300/Makefile b/share/man/man4/man4.hp300/Makefile
new file mode 100644
index 00000000000..2d78d5551a7
--- /dev/null
+++ b/share/man/man4/man4.hp300/Makefile
@@ -0,0 +1,9 @@
+#	from: @(#)Makefile	5.1 (Berkeley) 6/29/90
+#	$Id: Makefile,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+
+MAN=	autoconf.4 cons.4 ct.4 dca.4 dcl.4 dcm.4 dv.4 gb.4 grf.4 hil.4 \
+	intro.4 ite.4 le.4 mem.4 ppi.4 rb.4 rd.4 rmp.4 tc.4
+MLINKS=	mem.4 kmem.4
+MANSUBDIR=/hp300
+
+.include <bsd.prog.mk>
diff --git a/share/man/man4/man4.hp300/autoconf.4 b/share/man/man4/man4.hp300/autoconf.4
new file mode 100644
index 00000000000..7314c89f6e2
--- /dev/null
+++ b/share/man/man4/man4.hp300/autoconf.4
@@ -0,0 +1,142 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)autoconf.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: autoconf.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt AUTOCONF 4 hp300
+.Os
+.Sh NAME
+.Nm autoconf
+.Nd diagnostics from the autoconfiguration code
+.Sh DESCRIPTION
+When
+.Tn UNIX
+bootstraps it probes the innards of the machine
+on which it is running
+and locates controllers, drives, and other devices, printing out
+what it finds on the console.  This procedure is driven by a system
+configuration table which is processed by
+.Xr config 8
+and compiled into each kernel.
+.Pp
+Autoconfiguration on the
+.Tn HP300 Ns s
+is similar to that on the
+.Tn VAX ,
+the primary difference is in the naming conventions.
+On the
+.Tn HP300 ,
+if devices exist which are not configured they will be ignored;
+if devices exist of unsupported type they will be ignored.
+.Pp
+Normally, the system uses the disk from which it was loaded as the root
+filesystem.
+If that is not possible,
+a generic system will use
+.Sq Li rd0
+if it exists.
+If such a system is booted with the
+.Dv RB_ASKNAME
+option (see
+.Xr reboot 2 ) ,
+then the name of the root device is read from the console terminal at boot
+time, and any available device may be used.
+.Sh DIAGNOSTICS
+.Bl -diag
+.It CPU type not configured.
+You tried to boot
+.Tn UNIX
+on a
+.Tn CPU
+type which it doesn't
+(or at least this compiled version of
+.Tn UNIX
+doesn't) understand.
+.Pp
+.It hpib%d at sc%d, ipl %d.
+An
+.Tn HP-IB
+was found at sc%d (the select code)
+with ipl%d (interrupt priority level).
+.Tn UNIX
+will call it hpib%d.
+.Pp
+.It %s%d: %s.
+.It %s%d at hpib%d, slave %d.
+An
+.Tn HP-IB
+disk or tape controller was found.
+For disks
+.Ql %s%d
+will look like
+.Sq Li rd0 ,
+for tapes like
+.Sq Li ct0 .
+The
+.Ql %s
+in the first line will be a product type like ``7945A'' or ``9144''.
+The slave number comes from the address select switches on the drive.
+.Pp
+.It grf0 csr 0x560000
+.It grf%d at sc%d
+A bit mapped display was found either at the ``internal'' address (first case)
+or at some ``external'' select code (second case).
+If it exists, the internal display will always be unit 0.
+.Pp
+.It %s%d at sc%d, ipl %d flags %d
+Another peripheral controller was found at the indicated select code
+and with indicated interrupt priority level.
+.Ql %s
+will be one of
+.Xr dca 4
+(single-port serial interfaces),
+.Xr dcm 4
+(four-port serial interfaces), or
+.Xr le 4
+.Pf ( Tn LAN
+cards).
+The slave number comes from the address select switches on the interface card.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr boot 8 ,
+.Xr config 8
+.Rs
+.%T 4.3BSD for the HP300
+.%O in the distribution documentation package
+.Re
+.Sh HISTORY
+The
+.Nm autoconf
+feature
+.Ud -beta
diff --git a/share/man/man4/man4.hp300/cons.4 b/share/man/man4/man4.hp300/cons.4
new file mode 100644
index 00000000000..64a8bdaabf0
--- /dev/null
+++ b/share/man/man4/man4.hp300/cons.4
@@ -0,0 +1,79 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)cons.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: cons.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CONS 4 hp300
+.Os
+.Sh NAME
+.Nm cons
+.Nd
+.Tn HP300
+console interface
+.Sh DESCRIPTION
+This release supports a
+.Dq virtual
+console device used for
+.Em kernel printf
+messages and accessed in user mode via
+.Pa /dev/console .
+It is virtual in the sense that it is attached to a hardware interface
+at boot time.
+Currently the choices are limited to:
+a bit-mapped display acting as an
+.Em internal terminal emulator
+.Dq Tn ITE ,
+the builtin serial interface
+.Xr dca 4 ,
+or a
+.Xr null 4
+console in that order.
+.Sh FILES
+.Bl -tag -width /dev/console
+.It Pa /dev/console
+.El
+.Sh SEE ALSO
+.Xr tty 4 ,
+.Xr reboot 8
+.Sh HISTORY
+The
+.Nm
+device
+.Ud
+.Sh BUGS
+You should be able to specify potential console devices at
+.Xr config 8
+time.
diff --git a/share/man/man4/man4.hp300/ct.4 b/share/man/man4/man4.hp300/ct.4
new file mode 100644
index 00000000000..43c39844eca
--- /dev/null
+++ b/share/man/man4/man4.hp300/ct.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ct.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ct.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt CT 4 hp300
+.Os
+.Sh NAME
+.Nm \&ct
+.Nd
+.Tn CS/80
+cartridge tape interface
+.Sh SYNOPSIS
+.Cd "tape ct0 at hpib? slave ?"
+.Sh DESCRIPTION
+The cartridge tape interface as found in the 7946 and 9144 products
+provides a standard tape drive interface as described in
+.Xr mtio 4
+with the following exceptions:
+.Bl -enum
+.It
+There is only one density.
+.It
+Only the
+.Dq raw
+interface is supported.
+.It
+The
+.Dv MTIOCTOP
+.Xr ioctl 2
+is limited.
+In particular, the command,
+.Dv MTFSR
+is not supported.
+.It
+The
+.Dv MTIOCGET
+.Xr ioctl
+is not supported.
+.It
+The record size for read and write operations must be between
+1K and 64K inclusive.
+.El
+.Pp
+Special files
+.Pa rct0
+through
+.Pa rct3
+refer to rewind on close interfaces to drives 0 to 3.
+Files
+.Pa rct4
+through
+.Pa rct7
+refer to no-rewind interfaces.
+Files
+.Pa rct8
+through
+.Pa rct11
+refer to streaming rewind on close interfaces. (Only 9144 type devices
+can stream.)
+Lastly,
+.Pa rct12
+through
+.Pa rct15
+refer to streaming no-rewind interfaces.
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr tp 1 ,
+.Xr mtio 4 .
+.Sh HISTORY
+The
+.Nm \&ct
+driver
+.Ud
+.Sh BUGS
+Read and writes of less than 1024 bytes will not behave as expected.
diff --git a/share/man/man4/man4.hp300/dca.4 b/share/man/man4/man4.hp300/dca.4
new file mode 100644
index 00000000000..3d6968f416d
--- /dev/null
+++ b/share/man/man4/man4.hp300/dca.4
@@ -0,0 +1,90 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dca.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dca.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DCA 4 hp300
+.Os
+.Sh NAME
+.Nm dca
+.Nd
+.Tn HP 98644A
+communications interface
+.Sh SYNOPSIS
+.Cd "device dca0 at scode9 flags 0x1"
+.Sh DESCRIPTION
+The
+.Tn 98644A
+is a single port
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interface with a single character buffer.
+Such an interface is built-in to all series 300 machines.
+.Pp
+Input and output for each line may set to one of following baud rates;
+50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600 or
+19200.
+.Pp
+An optional argument
+.Ar flags
+may be set to 1 if the line should be treated as hard-wired
+with carrier always present or 0 if modem control is desired.
+.Sh FILES
+.Bl -tag -width Pa
+.It Pa /dev/tty0
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dca%d: silo overflow.
+The single-character input
+.Dq silo
+has overflowed and incoming data has been lost.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Data loss is possible on busy systems with baud rates greater than 300.
+The
+.Nm dca
+has never been tested with modem control enabled or on anything but the
+built-in interface.
diff --git a/share/man/man4/man4.hp300/dcl.4 b/share/man/man4/man4.hp300/dcl.4
new file mode 100644
index 00000000000..6883f53522d
--- /dev/null
+++ b/share/man/man4/man4.hp300/dcl.4
@@ -0,0 +1,130 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dcl.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dcl.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DCL 4 hp300
+.Os
+.Sh NAME
+.Nm dcl
+.Nd
+.Tn HP
+98628A communications link
+.Sh SYNOPSIS
+.Cd "device dcl0 at scode? flags 0x1"
+.Sh DESCRIPTION
+The 98628A is a buffered
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications interface.
+It has one port with full modem control.
+.Pp
+Input and output for each line may set to one of following baud rates;
+0, 50, 75, 110, 134.5, 150, 200, 300, 600, 1200, 1800, 2400, 4800,
+9600, 19200.
+.Pp
+An optional argument
+.Ar flags
+may be set to 1 if the line should be treated as hard-wired with
+carrier always present, or to 0 if modem control is desired.
+.Pp
+Use
+.Tn HP
+cable "98626 & 98628 opts.002,
+.Tn RS232-C
+.Tn DCE CABLE ,
+5061-4216" to attach non-modem devices.
+Use
+.Tn HP
+cable "98626 & 98628 opts.001,
+.Tn RS232-C
+.Tn DTE CABLE ,
+5061-4215" to attach modems.
+.Pp
+The 98628A has a 256 byte input silo and a 256 output silo. Input interrupts
+happen on a per character basis.
+.Pp
+The high water and low water marks in the kernel tty routines are completely
+inappropriate for a device like this with a large input buffer.  Don't use
+tandem mode if possible.  A fast system can handle input at 19.2K baud without
+receive overflow.
+.Pp
+For output to devices that make heavy use of
+.Tn XON/XOFF
+a write size of less
+then 256 will improve performance marginally.
+.Sh FILES
+.Bl -tag -width /dev/ttyl[0-9] -compact
+.It Pa /dev/ttyl[0-9]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dcl%d: error 0x%x RESET CARD.
+Where the errors are encoded:
+.Bd -unfilled -offset indent
+0x06 card failure
+0x0d uart receive overflow
+0x0e receive overflow
+0x0f missing external clock
+0x10 cts false too long
+0x11 lost carrier
+0x12 activity timeout
+0x13 connection not established
+0x19 illegal databits/parity
+0x1a register address out of range
+0x1b register value out of range
+0x-- unknown error
+.Ed
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Breaks received at a faster rate then 1 break every second will be 
+recognized as a single break.
+.Pp
+Console use is not supported.
+.Pp
+The
+.Tn RS-422/423/499 ,
+.Tn MTS-DSN/DL
+modes of the card are not supported.
diff --git a/share/man/man4/man4.hp300/dcm.4 b/share/man/man4/man4.hp300/dcm.4
new file mode 100644
index 00000000000..291dd44e90d
--- /dev/null
+++ b/share/man/man4/man4.hp300/dcm.4
@@ -0,0 +1,103 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dcm.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dcm.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DCM 4 hp300
+.Os
+.Sh NAME
+.Nm dcm
+.Nd
+.Tn HP
+98642A communications multiplexer
+.Sh SYNOPSIS
+.Cd "device dcm0 at scode? flags 0xe"
+.Sh DESCRIPTION
+The
+.Tn 98642A
+is a four port
+.Tn EIA
+.Tn RS-232C
+.Pf ( Tn CCITT
+.Tn V.28 )
+communications
+multiplexer. The
+.Tn 98642A
+has three direct-connect ports and one port with
+full modem control.
+.Pp
+Input and output for each line may set to one of following baud rates;
+50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800,
+9600, 19200, 38400.
+.Pp
+.Ar Flags
+is usually specified as 0xe since 3 of the 4 ports (1-3) do not support
+modem control and should be treated as hard-wired with carrier always present.
+If port 0 does not have the need for modem control then flags can be specified
+as
+.Ql 0xf .
+.Pp
+Each port on the
+.Tn 98642A
+has a 128 byte input silo and a 16 byte output silo.
+Interrupts happen on a per character basis unless the interrupt
+rate for the card reaches 70 interrupts per second at which time the
+driver changes to a 16.7ms (60 interrupts per second) polling scheme until 
+the interrupt rate drops.
+.Sh FILES
+.Bl -tag -width /dev/tty0[0-9a-f] -compact
+.It Pa /dev/tty0[0-9a-f]
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It dcm%d port%d: silo overflow
+Input Silo has overflowed and incoming data
+has been lost.
+.Pp
+.It dcm%d port%d: uart overflow
+The 3 character buffer in the uart has
+overflowed.
+.El
+.Sh SEE ALSO
+.Xr tty 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Total throughput per card, all ports together, is limited to 76800 bits per
+second continuous input rate.
diff --git a/share/man/man4/man4.hp300/dv.4 b/share/man/man4/man4.hp300/dv.4
new file mode 100644
index 00000000000..9dc597272ff
--- /dev/null
+++ b/share/man/man4/man4.hp300/dv.4
@@ -0,0 +1,174 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)dv.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: dv.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt DV 4 hp300
+.Os
+.Sh NAME
+.Nm dv
+.Nd
+.Tn HP98730
+``DaVinci'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98730
+and 98731 graphics device, also known as
+the DaVinci.  This driver has not been tested with all possible
+combinations of frame buffer boards and scan boards installed in the device.
+The driver merely checks for the existence of the device and does minimal set
+up.
+.Pp
+The DaVinci can be configured at either the ``internal'' address
+(frame buffer address 0x200000, control register space address 0x560000)
+or at an external select code less than 32.
+At the internal address it will be the ``preferred'' console device
+(see
+.Xr cons 4 ) .
+The hardware installation manual describes the procedure for
+setting these values.
+.Pp
+A user process communicates to the device initially by means of
+.Xr ioctl 2
+calls.  For the
+.Tn HP-UX
+.Xr ioctl
+calls supported, refer to
+.Tn HP-UX
+manuals.
+The
+.Bx
+calls supported are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Ar grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the standard 98730, the number of planes should be 4.  The number of
+colors would therefore be 15, excluding black.  If one 98732A frame buffer
+board is installed, there will still be 4 planes, with the 4 planes on the
+colormap board becoming overlay planes.  With each additional 98732 frame
+buffer board 4 planes will be added up to a maximum of 32 planes total.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and frame buffer space. Once the device file is
+mapped, the frame buffer structure is accessible.  The structure describing
+the 98730 is defined in
+.Aq Pa hpdev/grf_dvreg.h .
+.El
+.Sh EXAMPLE
+This is a short segment of code showing how the device is opened and mapped
+into user process address space assuming that it is
+.Ql grf0 :
+.Bd -literal -offset indent
+struct dvboxfb *dvbox;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+(void) ioctl (disp_fd, GRFIOCOFF, 0);
+return -1;
+}
+dvbox = (dvboxfb *) Addr;                  /* Control Registers   */
+frame_buffer=(u_char *)Addr+gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/MAKEDEV.hpux -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt98730
+.It Pa /dev/ocrt98730
+.Tn HP-UX
+.Em starbase
+special files
+.It Pa /dev/MAKEDEV.hpux
+script for creating
+.Tn HP-UX
+special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+.Tn CE.utilities
+must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4 .
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+Not tested for all configurations of scan board and frame buffer memory boards.
diff --git a/share/man/man4/man4.hp300/gb.4 b/share/man/man4/man4.hp300/gb.4
new file mode 100644
index 00000000000..962bc2ea6c9
--- /dev/null
+++ b/share/man/man4/man4.hp300/gb.4
@@ -0,0 +1,185 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)gb.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: gb.4,v 1.1 1995/10/18 08:44:27 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt GB 4 hp300
+.Os
+.Sh NAME
+.Nm gb
+.Nd
+.Tn HP98700
+``Gatorbox'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98700
+and 98710 graphics devices, also known as
+the Gatorbox.  The term ``Gator'' will often be used, and it is not to be
+confused with ``Gator'' used in reference to an
+.Tn HP
+9837 or 200/237 machine.
+Also, the term Gatorbox is used for the 98700 alone, with the 98701 frame
+buffer memory or with the 98710 accelerator installed.  This driver merely
+checks for the existence of the device and does minimal set up, as it is
+expected the applications will initialize the device to their requirements.
+.Pp
+The 98700 can be used as the only graphics device on a system, in which case
+it will be used as the system console.  It can also be installed as a secondary
+display device.  For the first case, the
+.Tn HP
+.Tn 98287A M.A.D.
+interface card
+should be set to internal control space.  This will put the frame buffer at
+the DIO address 0x200000 and the control registers at 0x560000.
+At this address it will be the ``preferred'' console device (see
+.Xr cons 4 ) .
+For use as a secondary device,
+the 98287A should be set to frame buffer address 0x300000,
+and to an external select code.
+.Pp
+It should be noted that this configuration will conflict with the 98547
+display card which has a 2 megabyte frame buffer starting at address 0x200000.
+The 98700 should only be installed as a secondary device in a machine with a
+1 bit 98544 display card or 4 bit 98545 card.
+The
+.%T 98700H Installation Guide
+contains further configuration information.
+.Pp
+The
+.Xr ioctl 2
+calls supported by the
+.Bx
+system for the Gatorbox are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Em grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the standard 98700, the number of planes should be 4.  The number of
+colors would therefore be 15, excluding black.  With the 98701 option installed
+there will be another 4 planes for a total of 8, giving 255 colors.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.
+The frame buffer structure describing the 98700
+is given in
+.Aq Pa hpdev/grf_gbreg.h .
+.It Dv GRFIOCUNMAP
+Unmap Device
+.Pp
+Unmap control registers and framebuffer space.
+.Pp
+For further information about the use of ioctl see the man page.
+.El
+.Sh EXAMPLE
+A small example of opening, mapping and using the device is given below.
+For more examples of the details on the behavior of the device, see the device
+dependent source files for the X Window System, in the
+.Pa /usr/src/new/X/libhp.fb
+directory.
+.Bd -literal -offset indent
+struct gboxfb *gbox;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+(void) ioctl (disp_fd, GRFIOCOFF, 0);
+return -1;
+}
+gbox = (gboxfb *) Addr;                         /* Control Registers   */
+frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/crt98700 -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt98700
+.Tn HP-UX
+.Em starbase
+special file
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+The
+.Tn CE.utilities/Crtadjust
+programs must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/grf.4 b/share/man/man4/man4.hp300/grf.4
new file mode 100644
index 00000000000..733de76ac6b
--- /dev/null
+++ b/share/man/man4/man4.hp300/grf.4
@@ -0,0 +1,214 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)grf.4	5.3 (Berkeley) 7/31/91
+.\"	$Id: grf.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd July 31, 1991
+.Dt GRF 4 hp300
+.Os
+.Sh NAME
+.Nm grf
+.Nd
+.Tn HP
+graphics frame buffer device interface
+.Sh DESCRIPTION
+This is a generic description of the frame buffer device interface.
+The devices to which this applies are the 98544, 98545 and 98547
+Topcat display cards (also known as
+.Tn HP300H
+devices),
+the 98548, 98549 and 98550
+Catseye display cards,
+the 98700
+Gatorbox graphics box,
+the 98720
+Renaissance graphics box,
+and the 98730
+DaVinci graphics box.
+.Pp
+Use of the devices can be effectively approached from two directions.
+The first is through
+.Tn HP-UX
+.Em Starbase
+routines, the second is by direct control in the
+.Bx
+environment.
+In order to use the Starbase libraries,
+code must be compiled in an
+.Tn HP-UX
+environment, either by doing so on an
+.Tn HP-UX
+machine and transferring the binaries to the
+.Bx
+machine, or by compilation
+with the use of the
+.Xr hpux 1
+command.
+Applications using Starbase libraries have been run successfully
+on
+.Bx
+machines using both of these compilation techniques.
+.Pp
+Direct compilation,
+such as that used for the X Window System servers, has also been successful.
+Examples of some frame buffer operations can be found in
+the device dependent X Window system sources, for example the
+.Pa /usr/src/new/X/libhp.fb
+directory.  These files contain examples of device dependent color map
+initialization, frame buffer operations, bit moving routines etc.
+.Pp
+The basic programming of the
+.Nm grf Ns ?
+devices involves opening the device
+file, mapping the control registers and frame buffer addresses into user
+space, and then manipulating the device as the application requires.
+The address mapping is controlled by an
+.Xr ioctl 2
+call to map the device into user space, and an unmap call when finished.
+The ioctls supported by
+.Bx
+are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Em grfinfo
+structure, as defined in <hpdev/grfioctl.h>:
+.Bd -literal
+struct	grfinfo {
+	int	gd_id;		/* HPUX identifier */
+	caddr_t	gd_regaddr;	/* control registers physaddr */
+	int	gd_regsize;	/* control registers size */
+	caddr_t	gd_fbaddr;	/* frame buffer physaddr */
+	int	gd_fbsize;	/* frame buffer size */
+	short	gd_colors;	/* number of colors */
+	short	gd_planes;	/* number of planes */
+/* new stuff */
+	int	gd_fbwidth;	/* frame buffer width */
+	int	gd_fbheight;	/* frame buffer height */
+	int	gd_dwidth;	/* displayed part width */
+	int	gd_dheight;	/* displayed part height */
+	int	gd_pad[6];	/* for future expansion */
+};
+.Ed
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.
+.It Dv GRFIOCUNMAP
+Unmap Device
+.Pp
+Unmap control registers and framebuffer space.
+.El
+.Pp
+For further information about the use of ioctl see the man page.
+.Sh EXAMPLE
+This short code fragment is an example of opening some graphics device and
+mapping in the control and frame buffer space:
+.Bd -literal
+#define GRF_DEV <some_graphics_device>  /* /dev/grfN */
+{
+	struct fbstruct *regs;  /*  fbstruct = gboxfb, rboxfb, etc. */
+	u_char *Addr, frame_buffer;
+	struct grfinfo gi;
+	int disp_fd;
+
+	disp_fd = open(GRF_DEV,1);
+	if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+	(void) ioctl (disp_fd, GRFIOCON, 0);
+
+	Addr = (u_char *) 0;
+	if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+		(void) ioctl (disp_fd, GRFIOCOFF, 0);
+		return -1;
+	}
+	regs = (fbstruct *) Addr;               /* Control Registers   */
+	frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer mem */
+}
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/*crt*? -compact
+.It Pa /dev/grf?
+.Bx
+interface special files
+.It Pa /dev/*crt*
+.Tn HP-UX
+.Em starbase
+interface special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+The
+.Tn CE.utilities/Crtadjust
+programs must be used for each specific device.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr dv 4 ,
+.Xr gb 4 ,
+.Xr rb 4 ,
+.Xr tc 4 ,
+.Xr hil 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/hil.4 b/share/man/man4/man4.hp300/hil.4
new file mode 100644
index 00000000000..ff60307d48c
--- /dev/null
+++ b/share/man/man4/man4.hp300/hil.4
@@ -0,0 +1,380 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)hil.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: hil.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt HIL 4 hp300
+.Os
+.Sh NAME
+.Nm hil
+.Nd Human Interface Link device driver
+.Sh DESCRIPTION
+The Human Interface Link
+.Pq Tn HIL
+is the interface used by the Series
+300 computers to connect devices such as keyboards, mice, control knobs,
+and
+.Tn ID
+modules to the machine. 
+.Pp
+Special files
+.Pa /dev/hil[1-7]
+refer to physical
+.Tn HIL
+devices 1 through 7.
+.Pa /dev/hil0
+refers to the ``loop'' pseudo-device and is used for the queue
+allocation commands described below.
+In the current implementation,
+there can only be one keyboard and it must be the first device
+.Pq Li hil1 .
+.Pp
+The device file that corresponds to a particular
+.Tn HIL
+device is determined
+by the order of the devices on the loop. For instance, if the
+.Tn ID
+module
+is the second physical device on the loop, then
+.Pa /dev/hil2
+is the special
+file that should be used for communication with the module.
+.Pp
+Communication with an
+.Tn HIL
+device is begun with an
+.Em open
+system call.
+A process may open a device already opened by another process unless
+the process is operating in
+.Tn HP-UX
+compatibility mode
+in which case it requires exclusive use of the device, or
+another process has the device open and is using
+.Tn HP-UX
+style
+device access (see
+.Dv HILIOCHPUX
+below).
+.Pp
+Input data from a device are obtained in one of two ways.
+Processes may use an
+.Tn HP-UX
+style interface in which the
+.Xr read 2
+system call is used to get fixed-size input packets,
+or they can use a
+.Em shared-queue
+interface.
+The shared-queue interface avoids the system call overhead associated with
+the
+.Tn HP-UX
+read interface by sharing a region of memory between the system
+and a user process.
+This region consists of a circular list of 255 event packets,
+and a header containing the size of the queue, and its head and tail indices.
+The system deposits event data at the tail of the queue,
+a process extracts it from the head.
+Extracting an event is done by copying it from the queue and then updating
+the head appropriately (i.e. head = (head + 1) % qsize).
+It is up to the process to ensure that packets are removed from the
+queue quickly enough to prevent the queue from filling.
+The system, when it determines that the queue is full,
+will ignore future packets from the device.
+Devices are
+.Em mapped
+to queues via an
+.Xr ioctl 2.
+More than one device can be mapped to a single queue and one device can
+be mapped to several queues.
+Queues are implicitly unmapped by a
+.Xr fork 2
+and thus,
+cannot be shared between processes.
+.Pp
+Choosing the type of interface is done on a per device basis using
+an
+.Xr ioctl ,
+but each device can only have one interface at any given time.
+.Pp
+.Em Select
+may be used with either interface to detect when input data are present.
+With the read interface, selecting indicates when there is input for a
+given device.
+With the shared-queue interface, selecting on the loop pseudo-device
+.Pq Li hil0
+indicates when data are present from any device on any queue
+while selecting on an individual device indicates when data are present
+for that device on any queue.
+.Pp
+.Em Close
+shuts down the file descriptor associated with the
+.Tn HIL
+device.
+The last close (system-wide) of any device removes that device
+from all queues it was mapped to while the last close of the loop
+pseudo-device unmaps all devices and deallocates all queues.
+.Pp
+.Xr Ioctl 2
+is used to control the
+.Tn HIL
+device.
+The ioctl commands (see
+.Aq Pa hpdev/hilioctl.h )
+listed below are separated into two groups.
+The first are those which provide functions identical to
+.Tn HP-UX .
+Refer to
+.Xr hil 7
+in the
+.Tn HP-UX
+documentation for more
+complete descriptions of these ioctls.
+The second set of ioctls are specific to this implementation and are
+primarily related to the shared-queue interface.
+.Bl -tag -width HILIOCARO
+.It Dv HILIOCID
+Identify and Describe
+.Pp
+The device will return up to 11 bytes of information describing the
+type and characteristics of the device.
+At the very least, 2 bytes of information,
+the device
+.Tn ID ,
+and the Describe Record Header will be returned.
+Identical to the
+.Tn HP-UX
+.Dv HILID
+ioctl.
+.It Dv HILIOCSC
+Report Security Code
+.Pp
+Request the security code record from a device. The security code can
+vary from 1 byte to 15, and is only supported by some
+.Tn HIL
+devices.
+Identical to the
+.Tn HP-UX
+.Dv HILSC
+ioctl.
+.It Dv HILIOCRN
+Report Name
+.Pp
+An ascii string of up to 15 bytes in length that describes the device
+is returned.
+Identical to the
+.Tn HP-UX
+.Dv HILRN
+ioctl.
+.It Dv HILIOCRS
+Report Status
+.Pp
+An ascii string of up to 15 bytes in length that describes the current
+status of the device is returned.
+Identical to the
+.Tn HP-UX
+.Dv HILRS
+ioctl.
+.It Dv HILIOCED
+Extended Describe
+.Pp
+Additional information of up to 15 bytes is returned describing the device.
+This ioctl is similar to
+.Tn HILIOCID ,
+which must be used first
+to determine if the device supports extended describe.
+Identical to the
+.Tn HP-UX
+.Dv HILED
+ioctl.
+.It Dv HILIOCAROFF
+Disable Auto Repeat
+.Pp
+Turn off auto repeat on the keyboard while it is cooked mode.
+Identical to the
+.Tn HP-UX
+.Dv HILDKR
+ioctl.
+.It Dv HILIOCAR1
+Enable Auto Repeat
+.Pp
+Turn on auto repeat on the keyboard while it is in raw mode.
+The repeat rate is set to 1/30th of a second.
+Identical to the
+.Tn HP-UX
+.Dv HILER1
+ioctl.
+.It Dv HILIOCAR2
+Enable Auto Repeat
+.Pp
+Turn on auto repeat on the keyboard while it is in raw mode.
+The repeat rate is set to 1/60th of a second.
+Identical to the
+.Tn HP-UX
+.Dv HILER2
+ioctl.
+.Pp
+The following ioctls are specific to this implementation:
+.It Dv HILIOCBEEP
+Beep
+.Pp
+Generate a keyboard beep as defined by
+.Ar arg .
+.Ar Arg
+is a pointer to two bytes of information,
+the first is the duration of the beep (microseconds),
+the second is the frequency of the beep.
+.It Dv HILIOCALLOCQ
+Allocate Queue
+.Pp
+Allocate and map into user space,
+an
+.Tn HILQ
+structure as defined in
+.Aq Pa hpdev/hilioctl.h .
+.Ar Arg
+is a pointer to a
+.Ar hilqinfo
+structure (also described in
+.Aq Pa hpdev/hilioctl.h )
+consisting of a
+.Pa qid
+and an
+.Pa addr .
+If
+.Pa addr
+is non-zero it specifies where in the address space to map the queue.
+If zero, the system will select a convenient location and fill in
+.Pa addr .
+.Pa Qid
+is filled in by the system and
+is a small integer used to uniquely identify this queue.
+This ioctl can only be issued to the loop pseudo-device.
+.It Dv HILIOCFREEQ
+Free Queue
+.Pp
+Release a previously allocated
+.Tn HIL
+event queue,
+unmapping it from the user's address space.
+.Ar Arg
+should point to a
+.Ar hilqinfo
+structure which contains the
+.Ar qid
+of the queue to be released.
+All devices that are currently mapped to the queue are unmapped.
+This ioctl can only be issued to the loop pseudo-device.
+.It Dv HILIOCMAPQ
+Map Device to Queue
+.Pp
+Maps this device to a previously allocated
+.Tn HIL
+event queue.
+.Ar Arg
+is a pointer to an integer containing the
+.Ar qid
+of the queue.
+Once a device is mapped to a queue,
+all event information generated by the device will be placed
+into the event queue at the tail.
+.It Dv HILIOCUNMAPQ
+Unmap Device from Queue
+.Pp
+Unmap this device from a previously allocated
+.Tn HIL
+event queue.
+.Ar Arg
+is a pointer to an integer containing the
+.Ar qid
+for the queue.
+Future events from the device are no longer placed on the event queue.
+.It Dv HILIOCHPUX
+Use HP-UX Read Interface
+.Pp
+Use
+.Tn HP-UX
+semantics for gathering data from this device.
+Instead of placing input events for the device on a queue,
+they are placed, in
+.Tn HP-UX
+format, into a buffer from which they
+can be obtained via
+.Xr read 2 .
+This interface is provided for backwards compatibility.
+Refer to the
+.Tn HP-UX
+documentation for a description of the event packet.
+.El
+.Sh FILES
+.Bl -tag -width /dev/hil[2-7] -compact
+.It Pa /dev/hil0
+.Tn HIL
+loop pseudo device.
+.It Pa /dev/hil1
+.Tn HIL
+keyboard device.
+.It Pa /dev/hil[2-7]
+Individual
+.Tn HIL
+loop devices.
+.El
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such HIL loop device.
+.It Bq Er ENXIO
+HIL loop is inoperative.
+.It Bq Er EBUSY
+Another HP-UX process has the device open, or another
+.Bx
+process has the
+device open, and is using it in
+.Tn HP-UX
+mode.
+.It Bq Er EINVAL
+Invalid
+.Xr ioctl
+specification.
+.It Bq Er EMFILE
+No more shared queues available.
+.El
+.Sh HISTORY
+The
+.Nm
+interface
+.Ud
diff --git a/share/man/man4/man4.hp300/intro.4 b/share/man/man4/man4.hp300/intro.4
new file mode 100644
index 00000000000..db77f858f29
--- /dev/null
+++ b/share/man/man4/man4.hp300/intro.4
@@ -0,0 +1,139 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)intro.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: intro.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt INTRO 4 hp300
+.Os
+.Sh NAME
+.Nm intro
+.Nd introduction to special files and hardware support
+.Sh DESCRIPTION
+This section describes the special files, related driver functions,
+and networking support
+available in the system.
+In this part of the manual, the
+.Tn SYNOPSIS
+section of
+each configurable device gives a sample specification
+for use in constructing a system description for the
+.Xr config 8
+program.
+The
+.Tn DIAGNOSTICS
+section lists messages which may appear on the console
+and/or in the system error log
+.Pa /usr/adm/messages
+due to errors in device operation;
+see
+.Xr syslogd 8
+for more information.
+.Pp
+This section contains both devices
+which may be configured into the system
+and network related information.
+The networking support is introduced in
+.Xr netintro 4 .
+.Sh HP DEVICE SUPPORT
+This section describes the hardware supported on the
+.Tn HP
+9000/300 series.
+Software support for these devices comes in two forms.  A hardware
+device may be supported with a character or block
+.Em device driver ,
+or it may be used within the networking subsystem and have a
+.Em network interface driver .
+Block and character devices are accessed through files in the file
+system of a special type; see
+.Xr mknod 8 .
+Network interfaces are indirectly accessed through the interprocess
+communication facilities provided by the system; see
+.Xr socket 2 .
+.Pp
+A hardware device is identified to the system at configuration time
+and the appropriate device or network interface driver is then compiled
+into the system.  When the resultant system is booted, the
+autoconfiguration facilities in the system probe for the device
+and, if found, enable the software support for it.
+If a device does not respond at autoconfiguration
+time it is not accessible at any time afterwards.
+To enable a device which did not autoconfigure,
+the system will have to be rebooted.
+.Pp
+The autoconfiguration system is described in
+.Xr autoconf 4 .
+A list of the supported devices is given below.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr intro 4 ,
+.Xr autoconf 4 ,
+.Xr config 8 .
+.Rs
+.%T "Building 4.3 BSD UNIX Systems with Config (SMM:2)"
+.Re
+.Sh LIST OF DEVICES
+The devices listed below are supported in this incarnation of
+the system.  Pseudo-devices are not listed.
+Devices are indicated by their functional interface.
+Occasionally, new devices of a similar type may be added
+simply by creating appropriate table entries in the driver;
+for example, new
+.Tn CS/80
+drives.
+.Bl -column grf/ite -offset indent
+ct	7946/9144 CS/80 cartridge tape
+dca	98644 built-in serial interface
+dcl	HP 98628A communications link
+dcm	HP 98642A communications multiplexer
+dma	98620B DMA controller
+dv	HP98730 ``DaVinci'' device interface
+gb	 HP98700 ``Gatorbox'' device interface
+grf/ite	Topcat/Gatorbox/Renaissance frame buffer
+hil	HIL interface
+hpib	Built-in and 98625 HP-IB interface
+ite	HP Internal Terminal Emulator
+le	98643 Lance-based ethernet interface
+mem	main memory
+ppi	HP-IB printer/plotter interface
+rb	HP98720 ``Renaissance'' device interface
+rd	CS/80 disk interface
+rmp	HP Remote Maintenance Protocol family
+st	CCS SCSI tape drive
+tc	HP98544-98550 ``Topcat'' and ``Catseye'' device interface
+.El
+.Sh HISTORY
+The
+.Tn HP300
+.Nm intro
+appeared in
+.Bx 4.3 Reno .
diff --git a/share/man/man4/man4.hp300/ite.4 b/share/man/man4/man4.hp300/ite.4
new file mode 100644
index 00000000000..4ef50690a49
--- /dev/null
+++ b/share/man/man4/man4.hp300/ite.4
@@ -0,0 +1,171 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ite.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ite.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt ITE 4 hp300
+.Os
+.Sh NAME
+.Nm ite
+.Nd
+.Tn HP
+Internal Terminal Emulator
+.Sh DESCRIPTION
+.Tn TTY
+special files of the form ``ttye?''
+are interfaces to the
+.Tn HP ITE
+for bit-mapped displays as implemented under
+.Bx .
+An
+.Tn ITE
+is the main system console on most
+.Tn HP300
+workstations and
+is the mechanism through which a user communicates with the machine.
+If more than one display exists on a system,
+any or all can be used as
+.Tn ITE Ns s
+with the limitation that only the first
+one opened will have a keyboard (since only one keyboard is supported).
+.Pp
+.Tn ITE
+devices use the
+.Tn HP-UX
+.Sq Li 300h
+.Xr termcap 5
+or
+.Xr terminfo 5
+entries.
+However, as currently implemented,
+the
+.Tn ITE
+does not support the full range of
+.Tn HP-UX
+capabilities for this device.
+Missing are multiple colors, underlining, blinking, softkeys,
+programmable tabs, scrolling memory and keyboard arrow keys.
+The keyboard does not have any of the international character
+support of
+.Tn HP Ns 's
+.Tn NLS
+system.
+It does use the left and right
+.Em extend char
+keys as meta keys, in that it will set the eighth bit of the character code.
+.Pp
+Upon booting, the kernel will first look for an
+.Tn ITE
+device
+to use as the system console
+.Pq Pa /dev/console .
+If a display exists at any hardware address, it will be the console.
+The kernel looks for, in order:
+a 98544, 98545, or 98547 Topcat display,
+a 98700 Gatorbox at a supported address (see
+.Xr gb 4 ) ,
+or a 98720 Renaissance at a supported address (see
+.Xr rb 4 ) .
+Currently there is no
+.Tn ITE
+support for the
+98548, 98549, 98550 and 98556 boards.
+.Pp
+When activated as an
+.Tn ITE
+(special file opened),
+all displays go through a standard initialization sequence.
+The frame buffer is cleared,
+the
+.Tn ROM
+fonts are unpacked and loaded into off-screen storage and
+a cursor appears.
+The
+.Tn ITE
+initialization routine also sets the colormap entry used to white.
+Variable colors are not used, mainly for reasons of simplicity.
+The font pixels are all set to 0xff and the colormap entry corresponding
+to all planes is set to R=255, G=255 and B=255.
+The actual number of planes used to display the characters depends
+on the hardware installed.
+Finally, if the keyboard
+.Tn HIL
+device is not already assigned to another
+.Tn ITE
+device, it is placed in ``cooked'' mode and assigned to this
+.Tn ITE .
+.Pp
+On most systems,
+a display is used both as an
+.Tn ITE
+.Pf ( Pa /dev/ttye?
+aka
+.Pa /dev/console )
+and as a graphics device
+.Pq /dev/grf? .
+In this environment,
+there is some interaction between the two uses that should be noted.
+For example, opening
+.Pa /dev/grf0
+will deactivate the
+.Tn ITE ,
+that is, write over whatever may be on the
+.Tn ITE
+display.
+When the graphics application is finished and
+.Pa /dev/grf0
+closed,
+the
+.Tn ITE
+will be reinitialized with the frame buffer cleared
+and the
+.Tn ITE
+colormap installed.
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Sh SEE ALSO
+.Xr grf 4 ,
+.Xr hil 4 ,
+.Xr gb 4 ,
+.Xr rb 4 ,
+.Xr tc 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/le.4 b/share/man/man4/man4.hp300/le.4
new file mode 100644
index 00000000000..2f5beeb62ed
--- /dev/null
+++ b/share/man/man4/man4.hp300/le.4
@@ -0,0 +1,110 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)le.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: le.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt LE 4 hp300
+.Os
+.Sh NAME
+.Nm le
+.Nd
+.Tn HP AMD
+7990
+.Tn LANCE
+Ethernet interface
+.Sh SYNOPSIS
+.Cd "device le0 at scode?"
+.Sh DESCRIPTION
+The
+.Nm le
+interface provides access to a 10 Mb/s Ethernet network via the
+.Tn AMD
+7990
+.Tn LANCE
+Ethernet chip set.
+.Pp
+Each of the host's network addresses
+is specified at boot time with an
+.Dv SIOCSIFADDR
+.Xr ioctl .
+The
+.Xr le
+interface employs the address resolution protocol described in
+.Xr arp 4
+to dynamically map between Internet and Ethernet addresses on the local
+network.
+.Pp
+The use of ``trailer'' encapsulation to minimize copying data on
+input and output is supported by the interface but offers no advantage
+due to the large
+.Tn HP
+page size.
+The use of trailers is negotiated with
+.Tn ARP .
+This negotiation may be disabled, on a per-interface basis,
+by setting the
+.Dv IFF_NOTRAILERS
+flag with an
+.Dv SIOCSIFFLAGS
+.Xr ioctl .
+.Sh DIAGNOSTICS
+.Bl -diag
+.It le%d: hardware address %s.
+This is a normal autoconfiguration message noting the 6 byte physical
+ethernet address of the adapter.
+.Pp
+.It de%d: can't handle af%d.
+The interface was handed
+a message with addresses formatted in an unsuitable address
+family; the packet was dropped.
+.Pp
+The following message indicate a possible hardware error performing
+the indicated operation during autoconfiguration or initialization.
+.Pp
+.It le%d: init timeout, stat = 0x%x.
+The hardware did not respond to an initialize command during reset.
+The reset procedure continues anyway.
+.El
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr inet 4 ,
+.Xr arp 4
+.Sh HISTORY
+The
+.Nm le
+driver
+.Ud
diff --git a/share/man/man4/man4.hp300/mem.4 b/share/man/man4/man4.hp300/mem.4
new file mode 100644
index 00000000000..c2163a9b2db
--- /dev/null
+++ b/share/man/man4/man4.hp300/mem.4
@@ -0,0 +1,87 @@
+.\" Copyright (c) 1990, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)mem.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: mem.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt MEM 4 hp300
+.Os
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.Nd main memory
+.Sh DESCRIPTION
+The file
+.Nm /dev/mem
+is an interface to the physical memory of the
+computer.
+Byte offsets in this file are interpreted as physical memory addresses.
+Reading and writing this file is equivalent to reading and writing
+memory itself.
+An error will be returned if an attempt is made to reference
+an offset outside of
+.Nm /dev/mem .
+.Pp
+Kernel virtual memory is accessed via the file
+.Nm /dev/kmem
+in the same manner as
+.Nm /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Sh HP300
+On the
+.Tn HP300 ,
+the last byte of physical memory is always
+.Li 0xFFFFFFFF .
+Therefore, on an
+.Tn HP300
+with
+8Mb of memory, physical memory would start
+at
+.Li 0xFF800000 .
+On the
+.Tn HP300 ,
+kernel virtual memory runs from
+.Li 0
+to about
+.Li 0x2400000 .
+.Sh FILES
+.Bl -tag -width /dev/kmem -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh HISTORY
+The files
+.Nm mem
+and
+.Nm kmem
+appeared in
+.At v6 .
diff --git a/share/man/man4/man4.hp300/ppi.4 b/share/man/man4/man4.hp300/ppi.4
new file mode 100644
index 00000000000..555c4c957c0
--- /dev/null
+++ b/share/man/man4/man4.hp300/ppi.4
@@ -0,0 +1,83 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)ppi.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: ppi.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt PPI 4 hp300
+.Os
+.Sh NAME
+.Nm ppi
+.Nd
+.Tn HP-IB
+printer/plotter interface
+.Sh SYNOPSIS
+.Cd "device ppi0 at hpib0 slave 5"
+.Sh DESCRIPTION
+The
+.Nm ppi
+interface provides a means of communication with
+.Tn HP-IB
+printers and plotters.
+.Pp
+Special files
+.Pa ppi0
+through
+.Pa ppi7
+are used to access the devices, with the digit at the end
+of the filename referring to the bus address of the device.
+Current versions of the autoconf code can not probe for these
+devices, so the device entry in the configuration file must be
+fully qualified.
+.Pp
+The device files appear as follows:
+.Bd -literal -offset indent
+"crw-rw-rw-  1 root      11,   0 Dec 21 11:22 /dev/ppi"
+.Ed
+.Sh DIAGNOSTICS
+None.
+.Sh SEE ALSO
+.Xr hpib 4 .
+.Sh HISTORY
+The
+.Nm
+interface
+.Ud
+.Sh BUGS
+This driver is very primitive, it handshakes data out byte by byte.
+It should use
+.Tn DMA
+if possible.
diff --git a/share/man/man4/man4.hp300/rb.4 b/share/man/man4/man4.hp300/rb.4
new file mode 100644
index 00000000000..a476c698857
--- /dev/null
+++ b/share/man/man4/man4.hp300/rb.4
@@ -0,0 +1,177 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)rb.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: rb.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RB 4 hp300
+.Os
+.Sh NAME
+.Nm rb
+.Nd
+.Tn HP98720
+``Renaissance'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98720
+and 98721 graphics device, also known as
+the Renaissance.  This driver has not been tested with all possible
+combinations of frame buffer boards and scan boards installed in the device.
+The driver merely checks for the existence of the device and does minimal set
+up.
+.Pp
+The Renaissance can be configured at either the ``internal'' address
+(frame buffer address 0x200000, control register space address 0x560000)
+or at an external select code less than 32.
+At the internal address it will be the ``preferred'' console device
+(see
+.Xr cons 4 ) .
+The hardware installation manual describes the procedure for
+setting these values.
+.Pp
+A user process communicates to the device initially by means of
+.Xr ioctl 2
+calls.  For the
+.Tn HP-UX
+.Xr ioctl 2
+calls supported, refer to
+.Tn HP-UX
+manuals.
+The
+.Tn BSD
+calls supported are:
+.Bl -tag -width indent
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Ar grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the standard 98720, the number of planes should be 4.  The number of
+colors would therefore be 15, excluding black.  If one 98722A frame buffer
+board is installed, there will still be 4 planes, with the 4 planes on the
+colormap board becoming overlay planes.  With each additional 98722 frame
+buffer board 4 planes will be added up to a maximum of 32 planes total.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.  The structure describing
+the 98720 is defined in
+.Pa hpdev/grf_rbreg.h .
+.El
+.Sh EXAMPLE
+This is a short segment of code showing how the device is opened and mapped
+into user process address space assuming that it is grf0:
+.Bd -literal
+struct rboxfb *rbox;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+	(void) ioctl (disp_fd, GRFIOCOFF, 0);
+	return -1;
+}
+rbox = (rboxfb *) Addr;                         /* Control Registers   */
+frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/MAKEDEV.hpux -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt98720
+.It Pa /dev/ocrt98720
+.Tn HP-UX
+.Em starbase
+special files
+.It Pa /dev/MAKEDEV.hpux
+script for creating
+.Tn HP-UX
+special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+The
+.Tn HP-UX
+.Tn CE.utilities
+must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid ioctl specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4 .
+.Pp
+For extensive code examples using the
+Renaissance, see the X device dependent source.
+.Sh HISTORY
+The
+.Nm
+interface
+.Ud
+.Sh BUGS
+Not tested for all configurations of scan board and frame buffer memory boards.
diff --git a/share/man/man4/man4.hp300/rd.4 b/share/man/man4/man4.hp300/rd.4
new file mode 100644
index 00000000000..a6a59420c59
--- /dev/null
+++ b/share/man/man4/man4.hp300/rd.4
@@ -0,0 +1,321 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)rd.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: rd.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RD 4 hp300
+.Os
+.Sh NAME
+.Nm rd
+.Nd
+.Tn CS/80
+disk interface
+.Sh SYNOPSIS
+.Cd "master hpib? at scode?"
+.Cd "disk rd? at hpib? slave?"
+.Sh DESCRIPTION
+This is a generic
+.Tn CS/80
+disk driver.
+Only a small number of possible
+.Tn CS/80
+drives are supported,
+but others can easily be added by adding tables to the driver.
+It is a typical block-device driver; see
+.Xr physio 4 .
+.Pp
+The script
+.Xr MAKEDEV 8
+should be used to create the
+.Nm rd
+special files; consult
+.Xr mknod 8
+if a special file needs to be made manually.
+.Sh DISK SUPPORT
+The driver interrogates the controller
+to determine the type of drive attached.
+The driver recognizes the following drives:
+7912, 7914, 7933, 7936, 7937, 7945,
+.Tn 757A/B ,
+.Tn 7958A/B ,
+.Tn 7959B,
+7962, 7963, 9122, 9134, 7912, 7936,
+and 9122,
+not all of which have been tested.
+Special file names begin with
+.Sq Li rd
+and
+.Sq Li rrd
+for the block and character files respectively. The second
+component of the name, a drive unit number in the range of zero to
+seven, is represented by a
+.Sq Li ?
+in the disk layouts below. The last component of the name is the
+file system partition
+and is designated
+by a letter from
+.Sq Li a
+to
+.Sq Li h
+which also corresponds to a minor device number sets: zero to seven,
+eight to 15, 16 to 23 and so forth for drive zero, drive two and drive
+three respectively
+(see physio 4 ) .
+The location and size (in sectors) of the
+partitions for these drives:
+.Bl -column header diskx undefined length
+.Tn 7945/7946 No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	112	15904	1-142
+	rd?b	16016	20160	143-322
+	rd?c	0	108416	0-967
+	rd?d	16016	40320	143-502
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	36176	72240	323-967
+	rd?h	56336	52080	503-967
+
+.Tn 9134D No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	96	15936	1-166
+	rd?b	16032	13056	167-302
+	rd?c	0	29088	0-302
+	rd?d	undefined
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	undefined
+	rd?h	undefined
+
+.Tn 9122S No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	undefined
+	rd?b	undefined
+	rd?c	0	1232	0-76
+	rd?d	undefined
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	undefined
+	rd?h	undefined
+
+.Tn 7912P No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	0	15904	0-70
+	rd?b	16128	22400	72-171
+	rd?c	0	128128	0-571
+	rd?d	16128	42560	72-261
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	38528	89600	172-571
+	rd?h	58688	69440	262-571
+
+.Tn 7914CT/P No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	224	15904	1-71
+	rd?b	16128	40320	72-251
+	rd?c	0	258048	0-1151
+	rd?d	16128	64960	72-361
+	rd?e	81088	98560	362-801
+	rd?f	179648	78400	802-1151
+	rd?g	56448	201600	252-1151
+	rd?h	81088	176960	362-1151
+
+.Tn 7958A No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	252	16128	1-64
+	rd?b	16380	32256	65-192
+	rd?c	0	255276	0-1012
+	rd?d	16380	48384	65-256
+	rd?e	64764	100800	257-656
+	rd?f	165564	89712	657-1012
+	rd?g	48636	206640	193-1012
+	rd?h	64764	190512	257-1012
+
+.Tn 7957A No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	154	16016	1-104
+	rd?b	16170	24640	105-264
+	rd?c	0	159544	0-1035
+	rd?d	16170	42350	105-379
+	rd?e	58520	54824	380-735
+	rd?f	113344	46200	736-1035
+	rd?g	40810	118734	265-1035
+	rd?h	58520	101024	380-1035
+
+.Tn 7933H No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	598	16146	1-27
+	rd?b	16744	66976	28-139
+	rd?c	0	789958	0-1320
+	rd?d	83720	16146	140-166
+	rd?e	99866	165646	167-443
+	rd?f	265512	165646	444-720
+	rd?g	83720	706238	140-1320
+	rd?h	431158	358800	721-1320
+
+.Tn 9134L No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	80	15920	1-199
+	rd?b	16000	20000	200-449
+	rd?c	0	77840	0-972
+	rd?d	16000	32000	200-599
+	rd?e	undefined
+	rd?f	undefined
+	rd?g	36000	41840	450-972
+	rd?h	48000	29840	600-972
+
+.Tn 7936H No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	861	16359	1-19
+	rd?b	17220	67158	20-97
+	rd?c	0	600978	0-697
+	rd?d	84378	16359	98-116
+	rd?e	100737	120540	117-256
+	rd?f	220416	120540	256-395
+	rd?g	84378	516600	98-697
+	rd?h	341817	259161	397-697
+
+.Tn 7937H No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	1599	15990	1-10
+	rd?b	17589	67158	11-52
+	rd?c	0	1116102	0-697
+	rd?d	84747	15990	53-62
+	rd?e	100737	246246	63-216
+	rd?f	346983	246246	217-370
+	rd?g	84747	1031355	53-697
+	rd?h	593229	522873	371-697
+
+.Tn 7957B/7961B No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	126	16002	1-127
+	rd?b	16128	32760	128-387
+	rd?c	0	159894	0-1268
+	rd?d	16128	49140	128-517
+	rd?e	65268	50400	518-917
+	rd?f	115668	44226	918-1268
+	rd?g	48888	111006	388-1268
+	rd?h	65268	94626	518-1268
+
+.Tn 7958B/7962B No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	378	16254	1-43
+	rd?b	16632	32886	44-130
+	rd?c	0	297108	0-785
+	rd?d	16632	49140	44-173
+	rd?e	65772	121716	174-495
+	rd?f	187488	109620	496-785
+	rd?g	49518	247590	131-785
+	rd?h	65772	231336	174-785
+
+.Tn 7959B/7963B No partitions:
+.Sy	disk	start	length	cyls
+	rd?a	378	16254	1-43
+	rd?b	16632	49140	44-173
+	rd?c	0	594216	0-1571
+	rd?d	16632	65772	44-217
+	rd?e	82404	303912	218-1021
+	rd?f	386316	207900	1022-1571
+	rd?g	65772	528444	174-1571
+	rd?h	82404	511812	218-1571
+.El
+.Pp
+The eight partitions as given support four basic, non-overlapping layouts,
+though not all partitions exist on all drive types.
+.Pp
+In the first layout there are three partitions and a ``bootblock'' area.
+The bootblock area is at the beginning of the disk and holds
+the standalone disk boot program.
+The
+.Pa rd?a
+partition is for the root file system,
+.Pa rd?b
+is a paging/swapping area, and
+.Pa rd?g
+is for everything else.
+.Pp
+The second layout is the same idea,
+but has a larger paging/swapping partition
+.Pq Pa rd?d
+and
+a smaller ``everything else'' partition
+.Pq Pa rd?h .
+This layout is better for environments which run many large processes.
+.Pp
+The third layout is a variation of the second,
+but breaks the
+.Pa rd?h
+partition into two partitions,
+.Pa rd?e
+and
+.Pa rd?f .
+.Pp
+The final layout is intended for a large, single file system second disk.
+It is also used when writing out the boot program since it is the only
+partition mapping the bootblock area.
+.Sh FILES
+.Bl -tag -width /dev/rrd[0-7][a-h] -compact
+.It Pa /dev/rd[0-7][a-h]
+block files
+.It Pa /dev/rrd[0-7][a-h]
+raw files
+.El
+.Sh DIAGNOSTICS
+.Bl -diag
+.It "rd%d err: v%d u%d, R0x%x F0x%x A0x%x I0x%x, block %d"
+An unrecoverable data error occurred during transfer of the
+specified block on the specified disk.
+.El
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud
+.Sh BUGS
+The current disk partitioning is totally bogus.
+.Tn CS/80
+drives have 256 byte sectors which are mapped to 512 byte
+``sectors'' by the driver.
+Since some
+.Tn CS/80
+drives have an odd number of sectors per cylinder,
+the disk geometry used is not always accurate.
+.Pp
+The partition tables for the file systems should be read off of each pack,
+as they are never quite what any single installation would prefer,
+and this would make packs more portable.
+.Pp
+A program to analyze the logged error information (even in its
+present reduced form) is needed.
diff --git a/share/man/man4/man4.hp300/rmp.4 b/share/man/man4/man4.hp300/rmp.4
new file mode 100644
index 00000000000..341a30fb2b8
--- /dev/null
+++ b/share/man/man4/man4.hp300/rmp.4
@@ -0,0 +1,163 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)rmp.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: rmp.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt RMP 4 hp300
+.Os
+.Sh NAME
+.Nm rmp
+.Nd
+.Tn HP
+Remote Maintenance Protocol Family
+.Sh SYNOPSIS
+.Cd "options RMP"
+.Fd #include <sys/types.h>
+.Fd #include <sys/socket.h>
+.Fd #include <netrmp/rmp.h>
+.Fd #include <netrmp/rmp_var.h>
+.Ft int
+.Fn socket AF_RMP SOCK_RAW proto
+.Sh DESCRIPTION
+Hewlett-Packard's Remote Maintenance Protocol family is a collection
+of protocols layered atop
+.Tn IEEE  802.3 .
+The current implementation of the RMP family provides protocol support only
+for the
+.Dv SOCK_RAW
+socket type.
+As a result,
+.Xr sendto 2
+and
+.Xr recvfrom 2
+must be used to send and
+receive
+.Tn RMP
+packets.
+.Pp
+The format of an
+.Tn RMP
+packet is defined in the include file
+.Aq Pa netrmp/rmp_var.h .
+The
+.Tn RMP
+packet arrives encapsulated in an
+.Pf ( Tn HP
+extended)
+.Tn IEEE  802.2
+packet.
+The
+.Tn IEEE  802.2
+packet
+is preceded by the kernel address of an
+.Ar ifnet struct
+which is used to `route' a packet out the same interface it
+arrived on.
+Outgoing packets are encapsulated in a standard
+.Tn IEEE  802.3
+packet, while incoming packets have this information stripped away.
+.Sh ADDRESSING
+.Tn RMP
+.Pf ( Tn IEEE
+802.3) addresses are 6 octets in length (48 bytes).
+Sockets in the Remote Maintenance Protocol family use the following
+addressing structure:
+.Bd -literal -offset indent
+struct sockaddr_rmp {
+	short		srmp_family;
+	u_char		srmp_dhost[6];
+};
+.Ed
+.Sh PROTOCOLS
+The
+.Tn RMP
+protocol family supported by the operating system
+is currently comprised of the Boot Protocol
+.Pq Em proto= Ns Dv RMPPROTO_BOOT .
+Unfortunately, we have no documentation on the Remote Maintenance
+Protocol and only sketchy information about the Boot Protocol.
+.Sh SEE ALSO
+.Xr socket 2 ,
+.Xr bind 2 ,
+.Xr sendto 2 ,
+.Xr recvfrom 2 ,
+.Xr intro 4 ,
+.Xr rbootd 8
+.Rs
+.%T "An Advanced 4.3 BSD Interprocess Communication Tutorial"
+.Re
+.Sh HISTORY
+The
+.Nm
+protocol interface
+.Ud
+.Sh BUGS
+.Bl -bullet
+.It
+The
+.Tn HP ROM
+uses
+.Tn IEEE
+802.3 (as opposed to Ethernet) packets.  While the
+kernel heuristically recognizes these packets, a more general mechanism
+for doing so should be provided.
+.It
+The
+.Tn HP ROM
+uses a multicast address when first trying to locate boot
+servers.  While the Ethernet [sic] board is programmed to recognize
+this particular multicast address (9:0:9:0:0:4), a more general
+mechanism for doing so should be provided.
+.It
+The kernel supports only
+.Tn RAW
+sockets for the
+.Tn RMP
+protocol.
+This is either a bug or a feature, since the kernel is smaller at the
+price of greater complexity in the server.
+.It
+There is no support for
+.Xr bind Ns 'ing
+an address in the
+.Tn RMP
+domain.
+Something like an
+.Dv RMPADDR_ANY
+should be provided to prevent more than one
+.Xr rbootd
+server from running at the same time.
+.El
diff --git a/share/man/man4/man4.hp300/st.4 b/share/man/man4/man4.hp300/st.4
new file mode 100644
index 00000000000..0d6092cbdd4
--- /dev/null
+++ b/share/man/man4/man4.hp300/st.4
@@ -0,0 +1,234 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)st.4	5.3 (Berkeley) 7/31/91
+.\"	$Id: st.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd July 31, 1991
+.Dt ST 4 hp300
+.Os
+.Sh NAME
+.Nm \&st
+.Nd
+.Tn CCS SCSI
+tape driver
+.Sh SYNOPSIS
+.Cd "tape st0 at scsi? slave ?"
+.Sh DESCRIPTION
+The
+.Nm \&st
+driver was written especially to support the Exabyte
+.Tn EXB-8200 8MM
+Cartridge 
+Tape Subsystem.  It has several extensions specific to the Exabyte,
+but should support other tape drives as long has they follow
+the
+.Tn ANSI SCSI-I
+specification.  Besides extensive use with
+an Exabyte, the driver has been tested with an
+Archive
+.Tn QIC-24
+tape drive.
+The
+.Nm \&st
+tape interface provides a standard tape drive interface 
+as described in
+.Xr mtio 4
+with the following exceptions:
+.Bl -enum
+.It
+Density is dependent on device type.  Current Exabyte hardware has
+only one density. The
+.Tn EXB-8500
+drive, when released, will have a high
+density format of
+.Tn 5.6GB .
+On an Archive
+.Tn QIC-24
+drive the driver reads both
+.Tn QIC-11
+and
+.Tn QIC-24
+formats
+but writes only
+.Tn QIC-24 .
+.It
+Only the ``raw'' interface is supported.
+.El
+.Pp
+Special Exabyte Support:
+.Pp
+The
+.Dv MTIOCGET
+.Xr ioctl 2
+call on an Exabyte returns this structure:
+.Bd -literal
+struct	mtget {
+	short mt_type;   /* type of magtape device */
+	short mt_dsreg;  /* sc_flags */
+	short mt_erreg;  /* high 8 bytes error status */
+	/* low  8 bytes percentage of Rewrites
+	if writing, ECC errors if reading */
+	short mt_resid;  /* Mbyte until end of tape */
+};
+.Ed
+.Pp
+Bit 4 in the minor device number is used
+to select long filemarks or short filemarks. A long filemark occupies
+2.12 MBytes of space on the tape, while a short filemark occupies 488 KBytes.
+A long filemark includes an erase gap while the short filemark does not.
+The tape can be positioned on the
+.Tn BOT
+side of a long filemark allowing
+data to be appended with a write operation.  Since the short filemark does not
+contain an erase gap which would allow writing it is considered to be
+non-erasable.  If either type of filemark is followed by blank tape,
+data may be appended on its
+.Tn EOT
+side.
+.Pp
+Bit 5 in the minor device number selects fixed block mode with a block
+size of 1K.  Variable length records are the default if bit 5 is not
+set.
+.Pp
+For unit 0 here are the effects of minor device bits 2,3,4,5. For other
+units add the
+.Em unit#
+to each of the device names.
+.Bl -column norewind density filemarks -offset indent
+.Em norewind	high	short	fixed
+.Em 	density	filemarks	block mode
+rst0
+nrst0	X
+rst8		X
+nrst8	X	X
+rst16			X
+nrst16	X		X
+rst24		X	X
+nrst24	X	X	X
+rst32				X
+nrst32	X			X
+rst40		X		X
+nrst40	X	X		X
+rst48			X	X
+nrst48	X		X	X
+rst56		X	X	X
+nrst56	X	X	X	X
+.El
+.Sh SEE ALSO
+.Xr mt 1 ,
+.Xr tar 1 ,
+.Xr mtio 4 ,
+.Rs
+.%T EXB-8200 8MM Cartridge Tape Subsystem Interface User Manual.
+.Re
+.Sh HISTORY
+The
+.Nm \&st
+driver
+.Ud
+.Sh BUGS
+The
+.Tn HP
+98268
+.Tn SCSI
+controller hardware can not do odd length
+.Tn DMA
+transfers.  If odd length
+.Tn DMA I/O
+is requested the driver will use the
+"Program Transfer Mode" of the Fujitsu
+.Tn MB87030
+chip. Read requests are
+normally even length for which a
+.Tn DMA
+transfer is used. If, however, the
+driver detects that a odd length read has happened (when a even length
+was requested) it will issue the
+.Dv EIO
+error and the last byte of the read
+data will be 0x00. Odd length read requests must match the size of the
+requested data block on tape.
+.Pp
+The following only applies when using long filemarks. Short filemarks can
+not be overwritten.
+.Bd -filled -offset 4n
+Due to the helical scan and the erase mechanism, there is a writing
+limitation on Exabyte drives.
+.Dq Li tar r
+or
+.Dq Li tar u
+will not work
+.Pf ( Dq Li tar c
+is ok).  One can only start writing at  1) beginning of tape, 2) on the
+end of what was last written, 3) "front" side of a regular (long) filemark.
+Say you have a tape with 3 tar files on it, want to save the first
+file, and want to begin writing over the 2nd file.
+.Pp
+On a normal 1/4" or 1/2" drive you would do:
+.Pp
+.Li "mt fsf 1; tar cf /dev/nrst0 ..."
+.Pp
+but for an Exabyte you need to do:
+.Pp
+.Li "mt fsf 1; mt bsf 1; mt weof 1; tar cf /dev/nrst0 ..."
+.Pp
+The regular long filemark consists of an erased zone 3.8" long
+(needed to begin a write).  In this case, the first filemark is
+rewritten in place, which creates an erased zone
+.Em after
+it, clearing the
+way to write more on the tape.  The erase head is not helical.
+.Pp
+One can position a tape to the end of what was last written by reading
+until a
+.Tn \*qBLANK CHECK\*q
+error is returned.  Writing can be started at this
+point.  (This applies to both long and short filemarks.)  The tape does
+not become positioned somewhere down the "erased" area as does a
+conventional magtape.  One can issue multiple reads at the
+.Tn \*qBLANK CHECK\*q
+error, but the Exabyte stays positioned at the beginning of the
+blank area, ready to accept write commands.  File skip operations do
+not stop at blank tape and will run into old data or run to the end of
+the tape, so you have to be careful not to
+.Dq Li mt fsf too_many .
+.Ed
+.Pp
+Archive support gets confused if asked to moved more filemarks than there are
+on the tape.
+.Pp
+This man page needs some work.  Some of these are not really bugs,
+just unavoidable consequences of the hardware.
diff --git a/share/man/man4/man4.hp300/tc.4 b/share/man/man4/man4.hp300/tc.4
new file mode 100644
index 00000000000..040f3ba2a9d
--- /dev/null
+++ b/share/man/man4/man4.hp300/tc.4
@@ -0,0 +1,182 @@
+.\" Copyright (c) 1990, 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" This code is derived from software contributed to Berkeley by
+.\" the Systems Programming Group of the University of Utah Computer
+.\" Science Department.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"	This product includes software developed by the University of
+.\"	California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"     from: @(#)tc.4	5.2 (Berkeley) 3/27/91
+.\"	$Id: tc.4,v 1.1 1995/10/18 08:44:28 deraadt Exp $
+.\"
+.Dd March 27, 1991
+.Dt TC 4 hp300
+.Os
+.Sh NAME
+.Nm \&tc
+.Nd
+.Tn HP98544
+98550 ``Topcat'' and ``Catseye'' device interface
+.Sh DESCRIPTION
+This driver is for the
+.Tn HP98544 ,
+98545 and 98547 ``Topcat''
+and
+.Tn HP98548 ,
+98549, and 98550 ``Catseye'' display cards.
+This driver merely checks for the existence of the device
+and does minimal set up, as it is expected the applications will initialize
+the device to their requirements.
+The Topcat and Catseye are nearly identical in common usage and only the
+Topcat will be referred to from now on.
+.Pp
+The Topcat display cards are not user configurable.  If one is present on a
+system, it will always have a frame buffer address of 0x200000 and a control
+register address of 0x560000.  These are the
+.Tn HP
+series 300
+.Tn ITE
+(Internal
+Terminal Emulator) defaults.  The device can also be used as a graphics output
+device.
+.Pp
+The 
+.Xr ioctl 2
+calls supported by the
+.Bx
+system for the Topcat are:
+.Bl -tag -width GRFIOCGINFO
+.It Dv GRFIOCGINFO
+Get Graphics Info
+.Pp
+Get info about device, setting the entries in the
+.Ar grfinfo
+structure, as defined in
+.Aq Pa hpdev/grfioctl.h .
+For the 98544 or 98549,
+the number of planes should be 1, as they are monochrome devices.
+The number of planes for a 98545 is 4, translating to 15 colors,
+excluding black.
+The 98547 and 98548 cards have 6 planes, yielding 63 colors and black.
+The 98550 has 8 planes, yielding 255 colors and black.
+The displayed frame buffer size for the 98549 and 98550 is 2048 x 1024,
+for the others it is 1024 x 768.
+.It Dv GRFIOCON
+Graphics On
+.Pp
+Turn graphics on by enabling
+.Tn CRT
+output.  The screen will come on, displaying
+whatever is in the frame buffer, using whatever colormap is in place.
+.It Dv GRFIOCOFF
+Graphics Off
+.Pp
+Turn graphics off by disabling output to the
+.Tn CRT .
+The frame buffer contents
+are not affected.
+.It Dv GRFIOCMAP
+Map Device to user space
+.Pp
+Map in control registers and framebuffer space. Once the device file is
+mapped, the frame buffer structure is accessible.  The frame buffer structure
+describing Topcat/Catseye devices is defined in
+.Aq Pa hpdev/grf_tcreg.h .
+.El
+.Pp
+For further information about the use of
+.Xr ioctl
+see the man page.
+.Sh EXAMPLE
+A small example of opening, mapping and using the device is given below.
+For more examples of the details on the behavior of the device, see the device
+dependent source files for the X Window System, in the
+.Pa /usr/src/new/X/libhp
+directory.
+.Bd -literal 
+struct tcboxfb *tc;
+u_char *Addr, frame_buffer;
+struct grfinfo gi;
+int disp_fd;
+
+disp_fd = open("/dev/grf0",1);
+
+if (ioctl (disp_fd, GRFIOCGINFO, &gi) < 0) return -1;
+
+(void) ioctl (disp_fd, GRFIOCON, 0);
+
+Addr = (u_char *) 0;
+if (ioctl (disp_fd, GRFIOCMAP, &Addr) < 0) {
+	(void) ioctl (disp_fd, GRFIOCOFF, 0);
+	return -1;
+}
+tc = (tcboxfb *) Addr;                          /* Control Registers   */
+frame_buffer = (u_char *) Addr + gi.gd_regsize; /* Frame buffer memory */
+.Ed
+.Sh FILES
+.Bl -tag -width /dev/MAKEDEV.hpux -compact
+.It Pa /dev/grf?
+.Bx
+special file
+.It Pa /dev/crt9837
+.It Pa /dev/crt98550
+.Tn HP-UX
+.Em starbase
+special files
+.It Pa /dev/MAKEDEV.hpux
+script for creating
+.Tn HP-UX
+special files
+.El
+.Sh DIAGNOSTICS
+None under
+.Bx .
+.Tn HP-UX
+.Tn /usr/CE.utilities/Crtadjust
+programs must be used.
+.Sh ERRORS
+.Bl -tag -width [EINVAL]
+.It Bq Er ENODEV
+no such device.
+.It Bq Er EBUSY
+Another process has the device open.
+.It Bq Er EINVAL
+Invalid
+.Xr ioctl
+specification.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr grf 4
+.Sh HISTORY
+The
+.Nm
+driver
+.Ud