-# $OpenBSD: 4.4BSD.dist,v 1.31 1997/03/05 04:34:26 flipk Exp $
+# $OpenBSD: 4.4BSD.dist,v 1.32 1997/03/05 09:13:12 niklas Exp $
/set type=dir uname=root gname=wheel mode=0755
# .
# ./usr/share/doc/smm/01.setup
01.setup
-# ./usr/share/doc/smm/01.setup/tahoe
-tahoe
-# ./usr/share/doc/smm/01.setup/tahoe
-..
-
# ./usr/share/doc/smm/01.setup/vax
vax
# ./usr/share/doc/smm/01.setup/vax
# ./usr/share/man/cat4/sun3
..
-# ./usr/share/man/cat4/tahoe
-tahoe
-# ./usr/share/man/cat4/tahoe
-..
-
# ./usr/share/man/cat4/vax
vax
# ./usr/share/man/cat4/vax
# ./usr/share/man/cat8/sun3
..
-# ./usr/share/man/cat8/tahoe
-tahoe
-# ./usr/share/man/cat8/tahoe
-..
-
# ./usr/share/man/cat8/vax
vax
# ./usr/share/man/cat8/vax
# ./usr/share/man/man4/sun3
..
-# ./usr/share/man/man4/tahoe
-tahoe
-# ./usr/share/man/man4/tahoe
-..
-
# ./usr/share/man/man4/vax
vax
# ./usr/share/man/man4/vax
-# $OpenBSD: Makefile,v 1.18 1997/01/02 16:36:00 etheisen Exp $
+# $OpenBSD: Makefile,v 1.19 1997/03/05 09:13:15 niklas Exp $
# $NetBSD: Makefile,v 1.22.4.2 1996/07/18 00:51:10 jtc Exp $
-# @(#)Makefile 8.1 (Berkeley) 6/18/93
MAN= audio.4 acd.4 ahc.4 bpf.4 ccd.4 clnp.4 cltp.4 ddb.4 drum.4 esis.4 \
fd.4 icmp.4 idp.4 imp.4 inet.4 ip.4 ipl.4 iso.4 lkm.4 lo.4 \
MLINKS+=scsi.4 scsibus.4
MLINKS+=tty.4 cua.4
SUBDIR= man4.amiga man4.arm32 man4.atari man4.hp300 man4.i386 man4.mac68k \
- man4.pc532 man4.sparc man4.sun3 man4.tahoe man4.vax
+ man4.pc532 man4.sparc man4.sun3 man4.vax
.include <bsd.prog.mk>
+++ /dev/null
-# from: @(#)Makefile 5.4 (Berkeley) 5/11/90
-# $Id: Makefile,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-
-MAN= ace.4 autoconf.4 cons.4 cy.4 dr.4 enp.4 ik.4 intro.4 lp.4 mem.4 \
- mtio.4 vd.4 vx.4
-MLINKS= mem.4 kmem.4
-MANSUBDIR=/tahoe
-
-.include <bsd.prog.mk>
+++ /dev/null
-.\" Copyright (c) 1986, 1991 The 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: @(#)ace.4 6.5 (Berkeley) 3/27/91
-.\" $Id: ace.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt ACE 4 tahoe
-.Os BSD 4.2
-.Sh NAME
-.Nm ace
-.Nd
-.Tn ACC
-10 Mb/s Ethernet interface
-.Sh SYNOPSIS
-.Cd "device ace0 at vba? csr 0xffff0000 flags 0xfff80000 vector acecint acerint"
-.Sh DESCRIPTION
-The
-.Nm ace
-interface provides access to a 10 Mb/s Ethernet network through
-an
-.Tn ACC
-controller.
-.Pp
-The hardware has 32 kilobytes of dual-ported memory on the
-.Tn VERSAbus .
-This memory
-is used for internal buffering by the board, and the interface code reads
-the buffer contents directly through the
-.Tn VERSAbus .
-The address of this memory is given in the
-.Ar flags
-field
-in the configuration file.
-.Pp
-Each of the host's network addresses
-is specified at boot time with an
-.Dv SIOCSIFADDR
-.Xr ioctl 2 .
-The
-.Nm ace
-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 interface normally tries to use a
-.Dq trailer
-encapsulation
-to minimize copying data on input and output.
-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 .
-.Pp
-The device implements an exponential backoff algorithm
-when notified of a collision on the cable. This algorithm utilizes
-a table of random numbers setup by the system at boot time.
-The delay is done in the controller.
-.Sh DIAGNOSTICS
-.Bl -diag
-.It "ace%d: stray xmit interrupt, xnct %d."
-An unexpected transmission complete interrupt was received;
-the interrupt is ignored.
-.It "ace%d: can't handle af%d."
-The interface was handed
-a message with addresses formatted in an unsuitable address
-family; the packet was dropped.
-.El
-.Sh SEE ALSO
-.Xr intro 4 ,
-.Xr inet 4 ,
-.Xr arp 4
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-The hardware is not capable of talking to itself. The software
-implements local sending and broadcast by sending such packets to the
-loop interface. This is a kludge.
-.Pp
-The device doesn't autoconfigure its interrupt vector; it is set
-at 0x90 + eight times the unit number.
+++ /dev/null
-.\" Copyright (c) 1986, 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 6.3 (Berkeley) 3/27/91
-.\" $Id: autoconf.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt AUTOCONF 4 tahoe
-.Os BSD 4.3t
-.Sh NAME
-.Nm autoconf
-.Nd diagnostics from autoconfiguration code
-.Sh DESCRIPTION
-When
-.Tn UNIX
-bootstraps it probes the innards of the machine it is running
-on 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
-.Tn VERSAbus
-devices are located by probing to see if their control-status
-registers respond. If not, they are silently ignored. If the control
-status register responds but the device cannot be made to interrupt,
-a diagnostic warning will be printed on the console and the device
-will not be available to the system.
-.Pp
-A generic system may be built which picks its root device at boot time
-as the
-.Dq best
-available device.
-If such a system is booted with the
-.Dv RB_ASKNAME
-option of (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 vba%d at %x.
-A
-.Tn VERSAbus
-adapter was found and mapped into the
-address space of the operating system starting at virtual address
-.Sq Li %x .
-.Tn UNIX
-will call it
-.Sq Li vba%d .
-.It %s%d at vba%d drive %d.
-A tape formatter or a disk was found
-on the
-.Tn VERSAbus ;
-for disks
-.Sq Li %s%d
-will look like
-.Sq Li dk0 ,
-for tape formatters
-like
-.Sq Li yc1 .
-The drive number comes from the unit plug on the drive
-or in the tape formatter
-.Pf ( Em not
-on the tape drive; see below).
-.It %s%d at %s%d slave %d.
-Which would look like
-.Sq Li yc0 at cy0 slave 0% ,
-where
-.Em yc0
-is the name for the tape device and
-.Em cy0
-is the name
-for the formatter. A tape slave was found on the tape formatter at the
-indicated drive number (on the front of the tape drive).
-.Tn UNIX
-will call the device, e.g.,
-.Li cy0.
-.It %s%d at vba%d csr %x vec %x ipl %x.
-The device
-.Sq Li %s%d ,
-e.g.
-.Sq Li vd0
-was found on
-.Sq Li vba%d
-at control-status register address
-.Sq Li %x
-and with
-device vector
-.Sq Li %x .
-The device interrupted at priority level
-.Sq Li %x .
-.It %s%d at vba%d csr %x no interrupts.
-The device was found
-on
-.Sq Li vba%d
-at control-status register address
-.Sq Li %x ;
-no
-interrupts were configured for the device.
-.It %s%d at vba%d csr %x didn't interrupt.
-The device did not interrupt,
-likely because it is broken, hung, or not the kind of device it is advertised
-to be. The csr address is interpreted as described above.
-.It %s%d at %s%d slave %d.
-Which would look like
-.Sq Li dk0 at vd0 slave 0 ,
-where
-.Em dk0
-is the name of a disk drive and
-.Em vd0
-is the name
-of the controller.
-.El
-.Sh SEE ALSO
-.Xr config 8
-.Sh HISTORY
-The
-.Nm
-special file appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-Very few devices actually figure out their interrupt vector
-by forcing the device to interrupt. Only the upper megabyte of the
-.Tn VERSAbus
-address space is mapped into the system's virtual address space.
+++ /dev/null
-.\" Copyright (c) 1986, 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: @(#)cons.4 6.3 (Berkeley) 3/27/91
-.\" $Id: cons.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt CONS 4 tahoe
-.Os BSD 4.3t
-.Sh NAME
-.Nm cons ,
-.Nm CP ,
-.Nm remote
-.Nd Tahoe console interface
-.Sh DESCRIPTION
-The console is available to the processor through the console registers.
-It acts like a normal terminal, except that a
-.Dq Ic ~
-is used to transfer
-commands to the console processor when the front panel key switch is
-in the
-.Dq foo
-or
-.Dq bar
-position.
-When the console processor
-is in control, a
-.Ql #>
-prompt is displayed. To continue execution
-after halting the machine with
-.Ql ~h ,
-use
-.Ql r .
-.Bl -tag -width Ds
-.It Ic \&~h
-Halt the machine.
-.It Ic \&~b
-Force a reboot.
-.It Ic \&~r
-Continue execution after a
-.Ic \&~h .
-.El
-.Pp
-Refer to the Tahoe
-console processor handbook for the complete list of facilities available
-through the console processor.
-.Pp
-The
-.Nm CP
-device provides direct access to the console processor. The
-.Nm remote
-device is a secondary console terminal used for remote diagnosis;
-it is normally connected to a modem.
-.Sh FILES
-.Bl -tag -width /dev/consolexx -compact
-.It Pa /dev/console
-.It Pa /dev/CP
-.It Pa /dev/remote
-.El
-.Sh DIAGNOSTICS
-None.
-.Sh SEE ALSO
-.Xr kdb 4 ,
-.Xr tty 4 ,
-.Xr reboot 8
-.Rs
-.%T Console Processor Handbook
-.Re
-.Sh HISTORY
-The
-.Nm
-interface appeared in
-.Bx 4.3 tahoe .
+++ /dev/null
-.\" Copyright (c) 1986, 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: @(#)cy.4 6.4 (Berkeley) 3/27/91
-.\" $Id: cy.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt CY 4 tahoe
-.Os BSD 4.3t
-.Sh NAME
-.Nm cy
-.Nd Cipher/tapemaster magtape interface
-.Sh SYNOPSIS
-.Cd "controller cy0 at vba? csr 0xffff4000 vector cyintr"
-.Cd "device yc0 at cy0 drive 0"
-.Sh DESCRIPTION
-The Cipher
-.Tn F880 ,
-.Tn M990 Ns / Tapemaster
-combination provides a standard tape drive
-interface as described in
-.Xr mt 4 .
-The Cipher
-.Tn F880
-tape drive operates at 1600 or 3200
-.Tn BPI \-
-controlled by a switch on the drive.
-The Cipher
-.Tn M990
-operates at 1600, 3200 or 6250
-.Tn BPI \-
-controlled by switches on the front of the drive.
-.Pp
-The Tapemaster controller board is actually a Multibus controller
-accessed through a Halversa Multibus to
-.Tn VERSAbus
-converter card.
-.Sh DIAGNOSTICS
-.Bl -diag
-.It cy%d: %dkb buffer.
-The formatter was found to have a
-.Ql %d
-kilobyte buffer during autoconfiguration.
-.It cy%d: timeout or err during init, status=%b.
-The controller
-timed out or an error occurred on a nop command during autoconfiguration;
-the controller may be hung.
-.It cy%d: configuration failure, status=%b.
-The controller
-timed out or an error occurred on a configure command during
-autoconfiguration; the controller may be hung.
-.It yc%d: no write ring.
-An attempt was made to write on the tape drive
-when no write ring was present; this message is written on the terminal of
-the user who tried to access the tape.
-.It yc%d: not online.
-An attempt was made to access the tape while it
-was offline; this message is written on the terminal of the user
-who tried to access the tape.
-.It cy%d: i/o size too large.
-A read or a write request exceeded the
-maximum transfer size for the controller \- 32 kilobytes; this message
-is written on the terminal of the user who made the read or write request.
-.It yc%d: hard error bn%d status=%b.
-A tape error occurred
-at block
-.Em bn ;
-the cy error register is
-printed in hexadecimal with the bits symbolically decoded. Any error is
-fatal on non-raw tape; when possible the driver will have retried
-the operation which failed several times before reporting the error.
-For known errors, the trailing
-.Ql %s
-is one of the following:
-.Pp
-.Bl -diag -offset indent -compact
-.It timeout, timeout1, timeout2, timeout3, timeout4.
-Time out errors; this may be due to trying to read a blank tape
-or the controller failing to interrupt or the drive dropping off-line.
-.It non-existent memory.
-A controller transfer to memory timed out.
-.It blank tape.
-The controller detected a blank tape when
-data was expected.
-.It micro-diagnostic, missing diagnostic jumper.
-An error occurred in the micro-diagnostics or
-the diagnostic mode jumper was not installed while attempting to execute
-a diagnostics command.
-.It eot/bot detected.
-The controller unexpectedly encountered
-end-of-tape or beginning-of-tape during an operation.
-.It retry unsuccessful.
-An error occurred which could not be recovered by repeated retries.
-.It fifo over/under-flow.
-The controller was unable to transfer data to the drive fast enough.
-This usually occurs because a transfer was performed without using the
-controller's internal buffer.
-.It drive to controller parity error.
-A parity error was detected by the controller in data transferred
-between the drive and the controller's internal buffer.
-.It prom checksum.
-The controller thinks its
-.Tn PROM
-is corrupted.
-.It time out tape strobe (record length error).
-The controller timed out while looking for an inter-record gap.
-This usually occurs because the records on the tape are larger than
-expected (or can be handled).
-.It tape not ready.
-The drive does not respond; usually the power has been turned off
-or a cable has come off.
-.It write protected.
-A write ring was present in the tape when a write was attempted.
-.It invalid link pointer.
-An invalid pointer was encountered in a tape parameter block.
-.It unexpected file mark.
-A tape file mark was encountered while trying to read or space.
-.It invalid byte count.
-An invalid byte count parameter was encountered in a tape parameter
-block.
-.It unidentified hardware error.
-.It streaming terminated.
-These should not happen.
-.El
-.Pp
-.It yc%d: lost interrupt.
-The controller failed to respond with an interrupt signifying completion
-of the current command. The system will attempt to abort the
-outstanding command and reset the controller.
-.Pp
-.It cy%d: reset failed.
-The system was unable to reset the controller. This is normally preceded
-by another message from the driver.
-.El
-.Sh SEE ALSO
-.Xr mt 1 ,
-.Xr tar 1 ,
-.Xr mtio 4
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-The controller supports only 20-bit addresses. The only way the
-system can insure the controller will be able to address data
-to be transferred
-is to copy it into an intermediate buffer allocated in the first megabyte
-of system memory.
+++ /dev/null
-.\" Copyright (c) 1983, 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: @(#)dr.4 6.3 (Berkeley) 3/27/91
-.\" $Id: dr.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt DR 4 tahoe
-.Os BSD 4.2
-.Sh NAME
-.Nm dr
-.Nd Ikon
-.Tn DR-11W
-interface
-.Sh SYNOPSIS
-.Cd "device dr0 at vba? csr 0xffff8000 vector drintr"
-.Sh DESCRIPTION
-The
-.Nm dr
-driver provides access
-to an Ikon
-.Tn DR-11W
-.Tn DMA
-controller.
-Each minor device is a different controller.
-.Pp
-In addition to reading and writing, the following
-.Xr ioctl 2
-requests are available:
-.Bl -tag -width DRSETNORSTALL
-.It Dv DRWAIT
-Wait for an attention interrupt from the associated device.
-.It Dv DRPIOW
-Write to the programmed
-.Tn I/O
-register.
-.It Dv DRPACL
-Write to the pulse register.
-.It Dv DRDACL
-Set the ``ac-low'' bit in the next command sent to the
-.Tn DR-11W .
-.It Dv DRPCYL
-Set the ``cycle'' bit in the next command sent to the
-.Tn DR-11W .
-.It Dv DRDFCN
-Hold the function bits until the next command is issused.
-.It Dv DRRATN
-Reset the attention flag.
-.It Dv DRRDMA
-Reset the
-.Tn DMA
-complete flag.
-.It Dv DRSFCN
-Set the function bits in the control status register and,
-as a side effect, clear the interrupt enable flag.
-.It Dv DRRPER
-Reset the parity error flag.
-.It Dv DRSETRSTALL
-Set ``no stall'' mode for all subsequent reads.
-In no stall mode the driver will abort
-read requests that fail to complete before a user
-specified timeout expires.
-.It Dv DRSETNORSTALL
-Disable no stall mode for reads.
-.It Dv DRGETRSTALL
-Return true if in no stall mode for reads.
-.It Dv DRSETRTIMEOUT
-Set the value of the timeout used in no stall mode for
-reads. The time is specified in tenths of seconds.
-.It Dv DRGETRTIMEOUT
-Return the time until (in tenths of seconds) before a read
-is timed out when in no stall mode.
-.It Dv DRSETWSTALL
-Set ``no stall'' mode for all subsequent writes.
-In no stall mode the driver will abort
-write requests that fail to complete before a user
-specified timeout expires.
-.It Dv DRSETNOWSTALL
-Disable no stall mode for writes.
-.It Dv DRGETWSTALL
-Return true if in no stall mode for writes.
-.It Dv DRSETWTIMEOUT
-Set the value of the timeout used in no stall mode for
-writes. The time is specified in tenths of seconds.
-.It Dv DRGETRTIMEOUT
-Return the time until (in tenths of seconds) before a write
-is timed out when in no stall mode.
-.It Dv DRWRITEREADY
-Return 1 if the device can accept data, 0 otherwise
-(this is really the
-.Tn DR-11W A
-status bit).
-.It Dv DRREADREADY
-Return 1 if the device has data for the host to read,
-0 otherwise (this is really the
-.Tn DR-11W B
-status bit).
-.It Dv DRBUSY
-Return 1 if the device is busy, 0 otherwise.
-.It Dv DRRESET
-Reset the DR-11W.
-.It Dv DR11STAT
-Return the driver status and the contents of the
-.Tn DR-11W
-.Tn I/O registers. The
-eight words returned are, in order, the driver
-status flags, the contents of the control status
-register, the contents of the status register
-at the time of the last interrupt from the device,
-the contents of the programmed
-.Tn I/O data register,
-a combination of the address modifier used by the
-device in performing
-.Tn VERSAbus
-transfers and the
-interrupt vector used by the device, the contents
-of the range register, the contents of the rahi
-register, and the contents of the ralo register.
-.It Dv DR11LOOP
-Perform loopback testing (the loopback cable must
-be in place for this to work).
-.El
-.Sh FILES
-.Bl -tag -width /dev/dr[0-7]xx -compact
-.It Pa /dev/dr[0-7]
-standard devices
-.El
-.Sh DIAGNOSTICS
-Lots of them, none of them meaningful.
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-This driver needs to be rewritten.
+++ /dev/null
-.\" Copyright (c) 1986, 1991 The 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: @(#)enp.4 5.4 (Berkeley) 3/27/91
-.\" $Id: enp.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt ENP 4 tahoe
-.Os BSD 4.3t
-.Sh NAME
-.Nm enp
-.Nd
-.Tn CMC
-10 Mb/s Ethernet interface
-.Sh SYNOPSIS
-.Cd "device enp0 at vba? csr 0xfff40000 vector enpintr"
-.Sh DESCRIPTION
-The
-.Nm enp
-interface provides access to a 10 Mb/s Ethernet network through
-a
-.Tn CMC ENP-20
-controller.
-.Pp
-The hardware has 128 kilobytes of dual-ported memory on the
-.Tn VERSAbus .
-This memory
-is used for internal buffering by the board, and the interface code reads
-the buffer contents directly through the
-.Tn VERSAbus .
-The address of this memory is derived from the address specified
-in the configuration file.
-.Pp
-Each of the host's network addresses
-is specified at boot time with an
-.Dv SIOCSIFADDR
-.Xr ioctl 2 .
-The
-.Nm enp
-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 interface normally tries to use a
-.Dq trailer
-encapsulation
-to minimize copying data on input and output.
-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 .
-.Pp
-Associated with each interface is a character device which
-is used to dowload, start, and reset the firmware in the controller.
-Reading or writing the
-.Dq ram device
-reads or writes the writable
-control store in the controller. Two
-.Xr ioctl 2
-calls,
-.Dv ENPIOGO
-and
-.Dv ENPIORESET ,
-are used to start and reset the
-firmware.
-.Sh DIAGNOSTICS
-.Bl -diag
-.It enp%d: can't handle af%d.
-The interface was handed
-a message with addresses formatted in an unsuitable address
-family; the packet was dropped.
-.El
-.Sh SEE ALSO
-.Xr intro 4 ,
-.Xr inet 4 ,
-.Xr arp 4 ,
-.Xr enpload 8
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-The hardware is not capable of talking to itself. The software
-implements local sending and broadcast by sending such packets to the
-loop interface. This is a kludge.
-.Pp
-The link level firmware does not support setting the board's
-Ethernet address.
+++ /dev/null
-.\" Copyright (c) 1983, 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: @(#)ik.4 6.3 (Berkeley) 3/27/91
-.\" $Id: ik.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt IK 4
-.Os BSD 4.2
-.Sh NAME
-.Nm ik
-.Nd Evans and Sutherland Picture System 300 graphics device interface
-.Sh SYNOPSIS
-.Cd "device ik0 at vba? csr 0xfffb100 vector ikintr"
-.Sh DESCRIPTION
-The
-.Nm ik
-driver provides access
-to an Evans and
-Sutherland Picture System 300 through an Ikon
-.Tn DR-11W
-interface card.
-Each two minor device numbers are a different
-.Tn PS300 ;
-within a pair of device numbers the odd valued
-device is used for ``diagnostic'' purposes. That is,
-for even numbered minor devices, opening the device results
-in a
-.Tn PS300
-``attach'' request being performed while for
-odd numbered minor devices the attach request is not performed.
-.Pp
-All operations between the host and the
-.Tn PS300
-utilize
-.Tn DMA .
-The driver currently supports only physical
-.Tn I/O operations
-when reading and writing; this makes the device useless with
-standard Evans and Sutherland software.
-.Pp
-The interface provided by the interface is as
-.Ux Ns -like
-as possible.
-When a device is opened a
-.Tn PS300
-attach request is automatically
-performed. When a device is closed a detach is performed. Reads
-and writes result in physical
-.Tn I/O
-requests, but hide all the details
-of the physical
-.Tn I/O
-protocol. This is programming style is completely
-different from the
-.Tn VMS Ns -oriented
-qio-style interface supplied by Evans
-and Sutherland.
-.Pp
-Reads and writes to the device result in a physical
-.Tn I/O
-request
-to the
-.Tn PS300 .
-If a
-.Xr readv 2
-or
-.Xr writev 2
-call is used, each
-.Tn I/O
-request results in a single physical
-.Tn I/O
-request (i.e. the scatter-gather facilities are not supported).
-In normal operation, the address used in a physical
-.Tn I/O
-request
-is the current file offset as specified explicitly with
-.Xr lseek 2
-or implictly as a result of reading or writing the device.
-To specify an address to be used with each physical
-.Tn I/O
-request,
-the
-.Nm ik
-driver interprets the
-.Ar iov
-entries in a non-standard way. If
-.Ar iov_len
-is zero, then
-.Ar iov_base
-is interpreted as an address to be used in the physical
-.Tn I/O
-request. If the address has the
-.Dv PSIO_SYNC
-flag or-d into it,
-the physical
-.Tn I/O
-request is made as a ``write with sync''.
-All addresses and data presented to the driver should be in
-the byte order of the host; any byte swapping required to converse
-with the
-.Tn PS300
-is performed in the driver/controller.
-.Pp
-In addition to reading and writing, the following
-.Xr ioctl
-requests are available:
-.Bl -tag -width PSIOGETERROR
-.It Dv PSIOLOOKUP
-Perform a ``name lookup'' request. The
-.Ar pslookup
-structure passed indicates the symbol name to be looked up
-and contains the address returned by the
-.Tn PS300 .
-A zero
-address return indicates the symbol was undefined.
-.It Dv PSIOGETERROR
-In the event of an error, this request may be made to
-return a more detailed and, sometimes
-.Tn PS300 Ns -specific ,
-error code.
-.Sh FILES
-.Bl -tag -width /dec/ik[0-7]xx -compact
-.It Pa /dev/ik[0-7]
-auto-attach devices
-.It Pa /dev/ik[0-7]d
-diagnostic interfaces to devices
-.El
-.Sh DIAGNOSTICS
-.Bl -diag
-.It ik%d: bad cmd %x.
-An unknown or unsupported command was received by the host.
-.It ik%d: spurious interrupt, code %x.
-An unexpected interrupt was received from the
-.Tn PS300 ;
-the
-attention code from the
-.Tn PS300
-is printed.
-.It ik%d: timeout.
-A command failed to elicit a response within a reasonable
-time; the
-.Tn PS300
-probably crashed.
-.El
-.Sh HISTORY
-The
-Tahoe Version
-.Nm
-driver appeared in
-.Bx 4.2 .
-.Sh BUGS
-An invalid access (e.g. illegal address) to the
-.Tn PS300
-can
-cause the
-.Tn PS300
-to crash. It is not always possible to unwedge
-the
-.Tn PS300
-interface hardware hung by an
-.Tn I/O
-request.
+++ /dev/null
-.\" Copyright (c) 1986, 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 6.5 (Berkeley) 3/27/91
-.\" $Id: intro.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt INTRO 4 tahoe
-.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 in the system error log
-.Pa /var/log/messages
-due to errors in device operation.
-.Sh CCI DEVICE SUPPORT
-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 physio 4
-and
-.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
-on the
-.Tn VERSAbus
-and, if found, enable the software
-support for it. If a
-.Tn VERSAbus
-device does not respond at autoconfiguration
-time it is not accessible at any time afterwards. To
-enable a
-.Tn VERSAbus
-device which did not autoconfigure, the system will have to
-be rebooted.
-.Pp
-The autoconfiguration system is described in
-.Xr autoconf 4 .
-.Sh SEE ALSO
-.Xr autoconf 4 ,
-.Xr netintro 4 ,
-.Xr config 8
-.Sh LIST OF DEVICES
-The devices listed below are supported in this incarnation of
-the system. Devices are indicated by their functional interface.
-If second vendor products provide functionally identical interfaces
-they should be usable with the supplied software.
-.Bf Sy
-(Beware however that we promise the software works
-ONLY with the hardware indicated on the appropriate manual page.)
-.Ef
-.Pp
-.Bl -column cons
-ace ACC 10 Mb/s Ethernet controller
-cons Tahoe console interface
-cy Cypher tape drive interface
-dr Ikon DR-11W controller
-enp 3Com 10 Mb/s Ethernet controller
-ik Evans and Sutherland PS300 interface through an Ikon DR-11W
- controller
-vd CCI vd mass storage disk controller
-vx CCI vioc terminal multiplexor
-.El
-.Sh HISTORY
-The section 4
-.Nm
-appeared in
-.Bx 4.2 .
+++ /dev/null
-.\" Copyright (c) 1986, 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: @(#)lp.4 6.2 (Berkeley) 3/27/91
-.\" $Id: lp.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt LP 4 tahoe
-.Os 4.3t
-.Sh NAME
-.Nm lp
-.Nd line printer
-.Sh SYNOPSIS
-device lp on the
-.Tn VIOC-P
-.Sh DESCRIPTION
-The
-.Nm lp
-driver provides an interface to 4 serial
-printer lines.
-.Sh FILES
-.Bl -tag -width /dev/lpxx
-.It Pa /dev/lp
-.El
-.Sh SEE ALSO
-.Xr lpr 1 ,
-.Xr vioc 4
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Bx 4.3 tahoe .
+++ /dev/null
-.\" Copyright (c) 1986, 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 6.3 (Berkeley) 3/27/91
-.\" $Id: mem.4,v 1.1.1.1 1995/10/18 08:44:32 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt MEM 4 tahoe
-.Os
-.Sh NAME
-.Nm mem ,
-.Nm kmem ,
-.Nm vmem
-.Nd main memory
-.Sh DESCRIPTION
-The special 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.
-Only offsets within the bounds of
-.Nm /dev/mem
-are allowed.
-.Pp
-Kernel virtual memory is accessed through the interface
-.Nm /dev/kmem
-in the same manner as
-.Nm /dev/mem .
-Only kernel virtual addresses that are currently mapped to memory are allowed.
-.Pp
-The file
-.Nm /dev/vmem
-allows access to the mapped portion of the
-.Tn VERSAbus
-.Tn I/O
-space. On the Tahoe the upper megabyte
-of the physical address space is accessible through
-this file (0xfff00000 through 0xffffffff).
-Accesses to the upper 64 kilobytes of
-the
-.Tn I/O
-space result in
-.Tn VERSAbus
-transfers with a
-16-bit address (the offset in this region) and a
-.Dq No non-privileged short Tn I/O
-.Tn VERSAbus
-address modifier.
-Accesses to the remainder of the mapped region,
-result in
-.Tn VERSAbus
-transfers with a 24-bit address
-and a ``non-privileged standard''
-.Tn VERSAbus
-address
-modifier. This region is actually part of the region
-between 0xfeff0000 and 0xffff0000
-which generates
-.Tn VERSAbus
-transfers with a 24-bit address.
-Accesses to the remainder of the one gigabyte
-.Tn I/O
-space
-generate transfers that utilize a 32-bit address with
-a ``non-privileged extended'' address modifier. Any
-32-bit address generated by a cpu access to this part
-of the
-.Tn I/O
-space have the upper two bits zero; thus,
-for example, an access to physical address 0xfe000000
-causes the address 0x3e000000 to be supplied in the
-resultant
-.Tn VERSAbus
-read/write cycle.
-.Pp
-On the Tahoe, the
-base address for the
-per-process data of the current process
-is virtual address 0xbffff000.
-.Sh FILES
-.Bl -tag -width Pa -compact
-.It Pa /dev/mem
-.It Pa /dev/kmem
-.It Pa /dev/vmm
-.El
-.Sh HISTORY
-The
-.Nm mem ,
-.Nm kmem
-files appeared in
-.At v6 .
-The file
-.Nm vmem
-appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-Memory files are accessed one byte
-at a time, an inappropiate method for some
-device registers.
+++ /dev/null
-.\" Copyright (c) 1986, 1991 The 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: @(#)mtio.4 6.4 (Berkeley) 5/6/91
-.\" $Id: mtio.4,v 1.1.1.1 1995/10/18 08:44:33 deraadt Exp $
-.\"
-.Dd May 6, 1991
-.Dt MTIO 4
-.Os
-.Sh NAME
-.Nm mtio
-.Nd
-.Tn UNIX
-magtape interface
-.Sh DESCRIPTION
-The special files named
-.Pa /dev/cy0s ,
-...,
-.Pa /dev/cy15s
-are interfaces to the
-.Tn UNIX
-magtape drivers.
-For the
-Tahoe, these interfaces
-may be on the
-.Tn VERSABUS
-via a
-.Tn CIPHER
-tapemaster formatter
-.Xr cy 4 .
-The files
-.Pa cy0s ,
-...,
-.Pa cy15s
-are read/written in 25
-.Tn IPS ,
-The density (1600
-.Tn BPI
-or 3200
-.Tn BPI )
-is selected by a switch on the drive.
-The following table of device names
-applies to any of the transport/controller pairs.
-.Bl -column "rewindxxx" "No-rewindxxx" "rewindxxxx" "No-rewindxxxx" -offset indent
-.Em Rewind No-rewind Rewind No-rewind
-cy0s/rcy0s ncy0s/nrcy0s cy8s/rcy8s ncy8s/nrcy8s
-cy1s/rcy1s ncy1s/nrcy1s cy9s/rcy9s ncy9s/nrcy9s
-cy2s/rcy2s ncy2s/nrcy2s cy10s/rcy10s ncy10s/nrcy10s
-cy3s/rcy3s ncy3s/nrcy3s cy11s/rcy11s ncy11s/nrcy11s
-cy4s/rcy4s ncy4s/nrcy4s cy12s/rcy12s ncy12s/nrcy12s
-cy5s/rcy5s ncy5s/nrcy5s cy13s/rcy13s ncy13s/nrcy13s
-cy6s/rcy6s ncy6s/nrcy6s cy14s/rcy14s ncy14s/nrcy14s
-cy7s/rcy7s ncy7s/nrcy7s cy15s/rcy15s ncy15s/nrcy15s
-.El
-.Pp
-The rewind devices automatically rewind
-when the last requested read, write or seek has finished, or the end of the tape
-has been reached. The letter
-.Ql n
-is usually prepended to
-the name of the no-rewind devices.
-.Pp
-For compatibility with customary
-.Tn UNIX
-tape device
-names
-.Dq Em mt* ,
-the
-.Bo Pa n Bc Pa cy*s
-files are linked to appropriate
-.Bo Pa n Bc Em mt*
-files.
-.Pp
-Unix tapes are written in multiples of 1024 byte block
-records. Two end-of-file markers mark the end of a tape, and
-one end-of-file marker marks the end of a tape file.
-If the tape is not to be rewound it is positioned with the
-head in between the two tape marks, where the next write
-will over write the second end-of-file marker.
-.Pp
-All of the magtape devices may be manipulated with the
-.Xr mt 1
-command.
-.Pp
-A number of other
-.Xr ioctl 2
-operations are available
-on raw magnetic tape.
-The following definitions are from
-.Aq Pa sys/mtio.h :
-.Bd -literal
-/*
- * Structures and definitions for mag tape io control commands
- */
-
-/* structure for MTIOCTOP - mag tape op command */
-struct mtop {
- short mt_op; /* operations defined below */
- daddr_t mt_count; /* how many of them */
-};
-
-/* operations */
-#define MTWEOF 0 /* write an end-of-file record */
-#define MTFSF 1 /* forward space file */
-#define MTBSF 2 /* backward space file */
-#define MTFSR 3 /* forward space record */
-#define MTBSR 4 /* backward space record */
-#define MTREW 5 /* rewind */
-#define MTOFFL 6 /* rewind and put the drive offline */
-#define MTNOP 7 /* no operation, sets status only */
-#define MTCACHE 8 /* enable controller cache */
-#define MTNOCACHE 9 /* disable controller cache */
-
-/* structure for MTIOCGET - mag tape get status command */
-
-struct mtget {
- short mt_type; /* type of magtape device */
-/* the following two registers are grossly device dependent */
- short mt_dsreg; /* ``drive status'' register */
- short mt_erreg; /* ``error'' register */
-/* end device-dependent registers */
- short mt_resid; /* residual count */
-/* the following two are not yet implemented */
- daddr_t mt_fileno; /* file number of current position */
- daddr_t mt_blkno; /* block number of current position */
-/* end not yet implemented */
-};
-
-/*
- * Constants for mt_type byte. These are the same
- * for controllers compatible with the types listed.
- */
-#define MT_ISTS 0x01 /* TS-11 */
-#define MT_ISHT 0x02 /* TM03 Massbus: TE16, TU45, TU77 */
-#define MT_ISTM 0x03 /* TM11/TE10 Unibus */
-#define MT_ISMT 0x04 /* TM78/TU78 Massbus */
-#define MT_ISUT 0x05 /* SI TU-45 emulation on Unibus */
-#define MT_ISCPC 0x06 /* SUN */
-#define MT_ISAR 0x07 /* SUN */
-#define MT_ISTMSCP 0x08 /* DEC TMSCP protocol (TU81, TK50) */
-#define MT_ISCY 0x09 /* CCI Cipher */
-#define MT_ISCT 0x0a /* HP 1/4 tape */
-#define MT_ISFHP 0x0b /* HP 7980 1/2 tape */
-#define MT_ISEXABYTE 0x0c /* Exabyte */
-#define MT_ISEXA8200 0x0c /* Exabyte EXB-8200 */
-#define MT_ISEXA8500 0x0d /* Exabyte EXB-8500 */
-#define MT_ISVIPER1 0x0e /* Archive Viper-150 */
-#define MT_ISPYTHON 0x0f /* Archive Python (DAT) */
-#define MT_ISHPDAT 0x10 /* HP 35450A DAT drive */
-
-/* mag tape io control commands */
-#define MTIOCTOP _IOW('m', 1, struct mtop) /* do a mag tape op */
-#define MTIOCGET _IOR('m', 2, struct mtget) /* get tape status */
-#define MTIOCIEOT _IO('m', 3) /* ignore EOT error */
-#define MTIOCEEOT _IO('m', 4) /* enable EOT error */
-
-#ifndef KERNEL
-#define DEFTAPE "/dev/rmt12"
-#endif
-
-#ifdef KERNEL
-/*
- * minor device number
- */
-
-#define T_UNIT 003 /* unit selection */
-#define T_NOREWIND 004 /* no rewind on close */
-#define T_DENSEL 030 /* density select */
-#define T_800BPI 000 /* select 800 bpi */
-#define T_1600BPI 010 /* select 1600 bpi */
-#define T_6250BPI 020 /* select 6250 bpi */
-#define T_BADBPI 030 /* undefined selection */
-#endif
-.Ed
-.Sh FILES
-.Bl -tag -width /dev/nrcy? -compact
-.It Pa /dev/cy? ,
-.It Pa /dev/rcy?
-Rewind devices.
-.It Pa /dev/ncy? ,
-.It Pa /dev/nrcy?
-No-rewind devices.
-.It Pa /dev/[n]mt? ,
-.It Pa /dev/[n]rmt?
-Linked device names.
-.El
-.Sh SEE ALSO
-.Xr mt 1 ,
-.Xr tar 1 ,
-.Xr cy 4
+++ /dev/null
-.\" Copyright (c) 1986, 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: @(#)vd.4 6.4 (Berkeley) 3/27/91
-.\" $Id: vd.4,v 1.1.1.1 1995/10/18 08:44:33 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt VD 4 tahoe
-.Os
-.Sh NAME
-.Nm vd
-.Nd
-.Tn VERSAbus
-storage module controller/drives
-.Sh SYNOPSIS
-.Cd "controller vd0 at vba? csr 0xffff2000 vector vdintr"
-.Cd "disk dk0 at vd0 drive 0"
-.Sh DESCRIPTION
-This is a generic
-.Tn VERSAbus
-storage module disk driver for the
-Computer Consoles
-.Tn SMD
-.Pq Tn VDDC
-and
-.Tn SMD-E
-disk controllers.
-.Pp
-The
-.Nm vd
-driver is a fairly typical block
-.Tn I/O
-device, except
-raw block
-.Tn I/O
-counts must be a multiple of 1024 bytes,
-whether the actual sector size is 512 or 1024 bytes.
-Likewise,
-.Xr seek
-calls should specify a multiple of 1024 bytes.
-See
-.Xr physio 4 .
-.Pp
-The first sector of each disk contains a disk label
-containing geometry information and partition layouts (see
-.Xr disklabel 5 ) .
-This sector is normally write-protected, and disk-to-disk copies should
-avoid copying this sector.
-The label may be updated with
-.Xr disklabel 8 ,
-which can also be used to write-enable and write-disable the sector.
-.Sh DISK SUPPORT
-During autoconfiguration,
-as well as when a drive is opened after all partitions are closed,
-the first sector of the drive is examined for a disk label.
-If a label is found, the geometry of the drive and the partition tables
-are taken from it.
-If no label is found,
-The driver checks for a disk label on sector 0 of each drive
-during autoconfiguration.
-If no label is found,
-the driver tries to access the last track on each drive
-to determine the type of drive attached.
-The driver has default partition tables for
-seven different drives:
-.Tn CDC FSD
-(160
-.Tn MB ) ,
-.Tn CDC
-9766 (300
-.Tn MB ) ,
-.Tn CDC XFSD
-(340
-.Tn MB ) ,
-.Tn CDC
-515
-.Tn MB ,
-Fujitsu 360
-.Tn MB ,
-Fujitsu Eagle (440
-.Tn MB ) ,
-and Maxtor 340
-.Tn MB .
-If the drive is not recognized, a single small partition is created
-to allow a label to be written.
-.Pp
-The partition tables in the disk label and the
-.Pa disktab
-file specify partition offsets and sizes in sectors, which are 512 bytes
-on
-.Tn SMD
-drives and 1024 bytes on 5 1/4"
-.Tn ESDI
-drives.
-By convention,
-the ?a partition is normally used for the root file system or other small
-file system,
-and the ?b partition is used as a paging area.
-The ?c partition maps the rest of the pack,
-except the last 5 cylinders which are reserved for bad sector forwarding,
-and diagnostic use.
-.Sh FILES
-.Bl -tag -width /dev/dk[0-7][a-f]xx -compact
-.It Pa /dev/dk[0-7][a-f]
-dk block files
-.It Pa /dev/rdk[0-7][a-f]
-dk raw files
-.El
-.Sh DIAGNOSTICS
-.Bl -diag
-.It vd%d: %s controller.
-This message is printed during autoconfiguration to identify
-the type of controller, either
-.Tn VDDC
-or
-.Tn SMDE .
-.Pp
-.It vd%d: init error.
-During autoconfiguration the controller failed to respond to
-an initialize command.
-.Pp
-.It vd%d: diagnostic error.
-During autoconfiguration the controller failed to respond to
-a diagnostic command.
-.Pp
-.It dk%d: unknown drive type.
-The system was unable to identify the specified drive as
-one of the drives described above; the drive will not be
-configured.
-.Pp
-.It vd%d: drive %d: config error.
-The system encountered a hard error when it tried to configure
-a drive during autoconfiguration.
-.Pp
-.It vd%d: starting drives, wait ... .
-This message indicates the system is about to tell the
-controller to ``start'' the drives attached to it.
-.Pp
-.It dk%d: %s <ntrak %d, ncyl %d, nsec %d>.
-For each drive recognized during autoconfiguration the system
-prints a message of this form. The drive type is displayed
-as well as the geometry: tracks/cylinder, cylinders, and sectors/track.
-.Pp
-.It vd%d: lost interrupt.
-The system failed to receive an interrupt from the controller after
-submitting a request.
-The system attempts to abort the current request and simulate an
-interrupt to unwedge the controller.
-During processing of the simulated interrupt, a controller error
-will be reported as described below.
-.Pp
-.It vd%d: stray interrupt.
-The system received an unexpected interrupt; it is ignored.
-.Pp
-.It dk%d%c: write locked.
-An attempt was made to write to a drive that is physically write-protected.
-.Pp
-.It "dk%d%c: controller err %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x; resetting controller... retrying."
-.br
-.It "dk%d%c: drive err %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x; resetting drive... retrying."
-An attempted transfer resulted in a controller or drive error.
-The controller or drive is reset, and the transfer is attempted
-a second time.
-.Pp
-.It "dk%d%c: hard error %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x."
-An unrecoverable error was encountered. The filesystem block number reported
-is a logical sector number on the indicated partition;
-it is expressed using 1024-byte sectors.
-If the transfer involved multiple blocks, the block range is printed as well.
-The parenthesized fields list the actual disk sector number
-relative to the beginning of the drive
-(in 512- or 1024-byte blocks, as appropriate),
-as well as the cylinder, track and sector number of the block.
-The error status field of the device control
-block is printed in hexadecimal followed by a symbolic description.
-If this is an
-.Tn SMDE
-controller, the error code is also displayed.
-.Pp
-.It "dk%d%c: soft error %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d) status %b ecode %x."
-A recoverable error was detected by the controller.
-The fields are interpreted in the same way as those for hard errors.
-.Pp
-.It "dk%d%c: soft ecc %sing fsbn %d [of %d-%d] (dk%d bn %d cn %d tn %d sn %d)."
-A recoverable
-.Tn ECC
-error was detected and corrected by the controller
-during the indicated transfer.
-.Pp
-.It vd%d: drive %d: couldn't reset.
-The system was unable to reconfigure a drive during a controller reset.
-.Pp
-.It vd%d: controller timeout.
-The controller failed to complete an operation within a reasonable
-time. This message is usually followed by another message indicating
-what operation timed out; e.g. ``during config'' for a configuration
-command.
-.El
-.Sh SEE ALSO
-.Xr disklabel 5 ,
-.Xr disklabel 8
-.Sh HISTORY
-The
-.Nm
-driver appeared in
-.Bx 4.3 tahoe .
-.Sh BUGS
-Writes
-scribble on the tail of incomplete blocks.
-.Pp
-The system should use real disk sector numbers internally,
-instead of assuming 1024-byte sectors;
-errors should report filesystem block numbers using the actual sector size.
-Raw
-.Tn I/O
-should be permitted on any sector boundary.
+++ /dev/null
-.\" Copyright (c) 1986, 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: @(#)vx.4 6.3 (Berkeley) 3/27/91
-.\" $Id: vx.4,v 1.1.1.1 1995/10/18 08:44:33 deraadt Exp $
-.\"
-.Dd March 27, 1991
-.Dt VX 4 tahoe
-.Os
-.Sh NAME
-.Nm vx
-.Nd
-.TN VIOC-X
-communications multiplexor
-.Sh SYNOPSIS
-.Cd "device vx0 at vba? csr 0xfffe0000 vector vackint vcmdrsp vunsol"
-.Sh DESCRIPTION
-A
-.Tn VIOC-X
-provides 16 communication lines with partial modem control,
-adequate for
-.Tn UNIX
-dialup use.
-and may be set to run at any of 16 speeds; see
-.Xr tty 4 .
-.Sh FILES
-.Bl -tag -width /dev/tty[0-9][0-9]xx -compact
-.It Pa /dev/tty[0-9][0-9]
-.It Pa /dev/ttyd[0-9a-f]
-dialups
-.El
-.Sh DIAGNOSTICS
-.Bl -diag
-.It vx%d: vc proc err, ustat %x.
-.Pp
-.It vx%d: vc uqual err, uqual %x.
-.Pp
-.It vx%d: %d exceeds silo size.
-.Pp
-.It vx%d: receiver overrun.
-.Pp
-.It VIOC-BOP no. %d at %x.
-The system identified a vioc supporting the bit oriented protocol.
-The number
-.Em %d
-is the board number assigned by the system
-while the address
-.Em %x
-is the address of the command control
-block for the vioc.
-.It vx%d: unknown type %x.
-The system encountered a vioc of unknown type during autoconfiguration.
-.It vx%d: didn't respond to LIDENT.
-The device did not respond to the configuration command that
-sets the interrupt vectors and port configuration.
-.It vx%d: %s%s, ports %d-%d.
-This is informatory message printed during autoconfiguration
-indicating the type of hardware present the port configuration.
-.It vx%d: no buffers.
-All the command buffers were in use; this indicates the device
-is constipated for some reason.
-.It vx%d: setq overflow.
-An attempt to append a command to an existing command buffer
-failed because the buffer was full or the hardware doesn't
-support this facility.
-.It vx%d: cmd q overflow.
-An attempt to place a new command on the command queue failed
-because it was full. The device is either overloaded or hung
-up for some reason. If this happens, the system tries to
-reset the device to unwedge it.
-.It vx%d INTR ERR type %x v_dcd %x.
-An error was returned by the device in response to some command.
-The command identifier and data carrier detect mask are printed
-followed by the contents of the command buffer in error.
-.It vx%d: vcmdrsp interrupt.
-A command response interrupt was received from a bop (bit oriented
-protocol) vioc. This should not happen.
-.It vx%d: cmdresp debug.
-.Pp
-.It vx%d: vunsol from
-.Tn BOP .
-An unsolicited interrupt was received from a bop vioc. This should
-not happen.
-.It vx%d: interrupt q overflow.
-The queue of pending interrupts to be delivered to the vioc is
-full. This is probably due to the vioc being wedged. The system
-resets the vioc if this occurs.
-.It vx%d: reset....
-The system attempted to reset the vioc.
-.El
-.Sh SEE ALSO
-.Xr tty 4
-.Sh HISTORY
-The
-.Nm
-special file appeared in
-.Bx 4.3 tahoe .
-# $OpenBSD: Makefile,v 1.9 1996/09/28 05:13:32 downsj Exp $
+# $OpenBSD: Makefile,v 1.10 1997/03/05 09:13:17 niklas Exp $
# $NetBSD: Makefile,v 1.13 1996/03/28 21:36:40 mark Exp $
# @(#)Makefile 8.1 (Berkeley) 6/5/93
compat_svr4.8 diskless.8 intro.8 rc.8 \
sticky.8 update.8 yp.8 boot_config.8
SUBDIR= man8.amiga man8.arm32 man8.atari man8.hp300 man8.i386 man8.mac68k \
- man8.sparc man8.sun3 man8.tahoe man8.vax
+ man8.sparc man8.sun3 man8.vax
.include <bsd.prog.mk>
+++ /dev/null
-.\" Copyright (c) 1991 The 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: @(#)MAKEDEV.8 5.2 (Berkeley) 3/22/91
-.\" $Id: MAKEDEV.8,v 1.1.1.1 1995/10/18 08:44:41 deraadt Exp $
-.\"
-.TH MAKEDEV 8 "March 22, 1991"
-.UC 7
-.SH NAME
-MAKEDEV \- create system and device special files
-.SH SYNOPSIS
-MAKEDEV name ...
-.SH DESCRIPTION
-The shell script
-.IR MAKEDEV ,
-found in the ``/dev'' directory, is used to create the common special
-files.
-See
-.IR special (8)
-for a more complete discussion of special files.
-.PP
-.I MAKEDEV
-takes any number of device names as arguments, where the names are
-the common abbreviation for the device.
-There are two special devices, ``std'' and ``local''.
-The former creates the standard devices for the architecture.
-The latter is for devices specific to the local site, and
-executes the shell file ``MAKEDEV.local''.
-.PP
-The Tahoe supports the following devices.
-Where a device name is followed by a hash sign (``#''), the hash sign
-must be replaced by a unit number.
-.TP 10
-std
-the standard devices (CP, console, drum, fd/*, klog, kmem, mem, null,
-remote, stderr, stdin, stdout, tty, vmem)
-.br
-.ns
-.TP 10
-local
-configuration specific devices
-.br
-.ns
-.TP 10
-cy#
-Cipher
-.br
-.ns
-.TP 10
-dk#
-VDDC or SMDE disk on Versabus
-.br
-.ns
-.TP 10
-dr#
-IKON DR-11W
-.br
-.ns
-.TP 10
-enp#
-CMC Ethernet interface for loading RAM
-.br
-.ns
-.TP 10
-hd#
-VDDC or SMDE disk on VME
-.br
-.ns
-.TP 10
-ik#
-IKON DR-11W w/ E&S PS300
-.br
-.ns
-.TP 10
-mp#
-MPCC
-.br
-.ns
-.TP 10
-pty#
-set of 32 master and slave pseudo terminals
-.br
-.ns
-.TP 10
-vx#
-VIOC
-.SH FILES
-/dev The special file directory.
-.SH SEE ALSO
-.IR mknod (1),
-.IR intro (4),
-.IR config (8),
-.IR special (8)
+++ /dev/null
-# @(#)Makefile 5.1 (Berkeley) 3/22/91
-# $NetBSD: Makefile,v 1.5 1995/09/06 21:36:41 jtc Exp $
-
-MAN= MAKEDEV.8
-MLINKS= MAKEDEV.8 makedev.8
-MANSUBDIR=/tahoe
-
-.include <bsd.prog.mk>
projects / openbsd / commitdiff