BSD 4_1c_2 development

Work on file usr/man/man4/va.4v
Work on file usr/man/man4/vp.4v

Synthesized-from: CSRG/cd1/4.1c.2

diff --git a/usr/man/man4/va.4v b/usr/man/man4/va.4v
new file mode 100644 (file)
index 0000000..956de07
--- /dev/null
+++ b/usr/man/man4/va.4v
@@ -0,0 +1,139 @@
+.TH VA 4V "1 April 1981"
+.UC 4
+.SH NAME
+va \- Benson-Varian interface
+.SH SYNOPSIS
+.B "controller va0 at uba0 csr 0164000 vector vaintr"
+.br
+.B "disk vz0 at va0 drive 0"
+.SH DESCRIPTION
+(\fBNOTE: the configuration description, while counter-intuitive,
+is actually as shown above\fP.)
+.PP
+The Benson-Varian printer/plotter in normally used with the programs
+.IR vpr (1),
+.IR vprint (1)
+or
+.IR vtroff (1).
+This description is designed for those who wish to drive the Benson-Varian
+directly.
+.PP
+The Benson-Varian at Berkeley uses 11\*(rq by 8\*(rq fan-fold paper.
+It will print 132 characters per line in print mode
+and 2112 dots per line in plot mode.
+.PP
+In print mode, the Benson-Varian uses a modified ASCII character set.
+Most control characters print various non-ASCII graphics such as daggers,
+sigmas, copyright symbols, etc.
+Only LF and FF are used as format effectors.  LF acts as a newline,
+advancing to the beginning of the next line, and FF advances to the top of
+the next page.
+.PP
+In plot mode, the Benson-Varian prints one raster line at a time.
+An entire raster line of bits (2112 bits = 264 bytes) is sent, and
+then the Benson-Varian advances to the next raster line.
+.PP
+.B Note:
+The Benson-Varian must be sent an even number of bytes.
+If an odd number is sent, the last byte will be lost.
+Nulls can be used in print mode to pad to an even number of bytes.
+.PP
+To use the Benson-Varian yourself,
+you must realize that you cannot open the
+device,
+.I /dev/va0
+if there is a daemon active.
+You can see if there is a daemon active by doing a
+.IR ps (1),
+or by looking in the directory
+.IR /usr/spool/vad .
+If there is a file
+.I lock
+there, then there is probably a daemon
+.IR /usr/lib/vad
+running.
+If not, you should remove the
+.I lock.
+.PP
+To set the Benson-Varian into plot mode include the file
+.RI < sys/vcmd.h >
+and use the following
+.IR ioctl (2)
+call
+.IP
+ioctl(fileno(va), VSETSTATE, plotmd);
+.PP
+where
+.I plotmd
+is defined to be
+.IP
+\fBint\fR plotmd[] = { VPLOT, 0, 0 };
+.PP
+and
+.I va
+is the result of a call to
+.I fopen
+on stdio.
+When you finish using the Benson-Varian in plot mode you should advance to
+a new page
+by sending it a FF after putting it back into print mode, i.e. by
+.PP
+'nf
+       \fBint\fR prtmd[] = { VPRINT, 0, 0 };
+       \&...
+       fflush(va);
+       ioctl(fileno(va), VSETSTATE, prtmd);
+       write(fileno(va), "\ef\e0", 2);
+.fi
+.PP
+.BR N.B. :
+If you use the standard I/O library with the Benson-Varian you
+.B must
+do
+.IP
+setbuf(vp, vpbuf);
+.PP
+where
+.I vpbuf
+is declared
+.IP
+\fBchar\fR vpbuf[BUFSIZ];
+.PP
+otherwise the standard I/O library, thinking that the Benson-Varian
+is a terminal (since it is a character special file) will not adequately buffer
+the data you are sending to the Benson-Varian.
+This will cause it to run
+.B extremely
+slowly and tend to grind the system to a halt.
+.SH FILES
+/dev/va0
+.SH SEE ALSO
+vfont(5),
+vpr(1),
+vtroff(1),
+vp(4V)
+.SH DIAGNOSTICS
+The following error numbers are significant at the
+time the device is opened.
+.TP 10
+[ENXIO]
+The device is already in use.
+.TP
+[EIO]
+The device is offline.
+.PP
+The following message may be printed on the console.
+.PP
+\fBva%d: npr timeout\fR.  The device was not able to get data from
+the UNIBUS within the timeout period, most likely because some other
+device was hogging the bus.  (But see BUGS below).
+.SH BUGS
+The 1's (one's) and l's (lower-case el's) in the Benson-Varian's
+standard character set look very similar; caution is advised.
+.PP
+The interface hardware is rumored to have problems which can
+play havoc with the UNIBUS.  We have intermittent minor problems on the
+UNIBUS where our
+.I va
+lives, but haven't ever been able to pin them down
+completely.

diff --git a/usr/man/man4/vp.4v b/usr/man/man4/vp.4v
new file mode 100644 (file)
index 0000000..d26691e
--- /dev/null
+++ b/usr/man/man4/vp.4v
@@ -0,0 +1,112 @@
+.TH VP 4V "10 May 1981"
+.UC 4
+.SH NAME
+vp \- Versatec interface
+.SH SYNOPSIS
+.B "device vp0 at uba0 csr 0177510 vector vpintr vpintr"
+.SH DESCRIPTION
+The Versatec printer/plotter is normally used with the programs
+.IR vpr (1),
+.IR vprint (1)
+or
+.IR vtroff (1).
+This description is designed for those who wish to drive the Versatec directly.
+.PP
+The Versatec at Berkeley is 36\*(rq wide, and has 440 characters per line
+and 7040 dots per line in plot mode (this is actually slightly less than
+36\*(rq of dots.)
+The paper used is continuous roll paper, and comes in 500' rolls.
+.PP
+To use the Versatec yourself, you must realize that you cannot open the
+device,
+.I /dev/vp0
+if there is a daemon active.
+You can see if there is a daemon active by doing a
+.IR ps (1),
+or by looking in the directory
+.I /usr/spool/vpd.
+If there is a file
+.I lock
+there, then there is probably a daemon
+.I /usr/lib/vpd
+running.
+If not, you should remove the
+.I lock.
+.PP
+To set the Versatec into plot mode you should include
+.RI < vcmd.h >
+and use the
+.IR ioctl (2)
+call
+.IP
+ioctl(fileno(vp), VSETSTATE, plotmd);
+.PP
+where
+.I plotmd
+is defined to be
+.IP
+\fBint\fR plotmd[] = { VPLOT, 0, 0 };
+.PP
+and
+.I vp
+is the result of a call to
+.I fopen
+on stdio.
+When you finish using the Versatec in plot mode you should eject paper
+by sending it a EOT after putting it back into print mode, i.e. by
+.PP
+'nf
+       \fBint\fR prtmd[] = { VPRINT, 0, 0 };
+       \&...
+       fflush(vp);
+       ioctl(fileno(vp), VSETSTATE, prtmd);
+       write(fileno(vp), "\e04", 1);
+.fi
+.PP
+.BR N.B. :
+If you use the standard I/O library with the Versatec you
+.B must
+do
+.IP
+setbuf(vp, vpbuf);
+.PP
+where
+.I vpbuf
+is declared
+.IP
+\fBchar\fR vpbuf[BUFSIZ];
+.PP
+otherwise the standard I/O library, thinking that the Versatec
+is a terminal (since it is a character special file) will
+not adequately buffer
+the data you are sending to the Versatec.
+This will cause it to run
+.B extremely
+slowly and tends to grind the system to a halt.
+.SH FILES
+/dev/vp0
+.SH SEE ALSO
+vfont(5),
+vpr(1),
+vtroff(1),
+va(4V)
+.SH DIAGNOSTICS
+The following error numbers are significant at the
+time the device is opened.
+.TP 10
+[ENXIO]
+The device is already in use.
+.TP
+[EIO]
+The device is offline.
+.SH BUGS
+The configuration part of the driver assumes that the device is setup to
+vector print mode through 0174 and plot mode through 0200.  Since the
+driver doesn't care whether the device considers the interrupt to be
+a print or a plot interrupt, it would be preferable to have these be
+the same.  This since the configuration program can't be sure at boot
+time which vector interrupted and where the interrupt vectors actually are.
+For the time being, since our versatec is vectored as described above,
+we specify that it has two interrupt vectors and are careful to detect
+an interrupt through 0200 at boot time and (manually) pretend the interrupt
+came through 0174.