xref: /netbsd-src/share/man/man4/man4.vax/vp.4 (revision 3b01aba77a7a698587faaae455bbfe740923c1f5)
1.\"	$NetBSD: vp.4,v 1.8 2001/04/11 19:21:18 wiz Exp $
2.\"
3.\" Copyright (c) 1980, 1991, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by the University of
17.\"	California, Berkeley and its contributors.
18.\" 4. Neither the name of the University nor the names of its contributors
19.\"    may be used to endorse or promote products derived from this software
20.\"    without specific prior written permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32.\" SUCH DAMAGE.
33.\"
34.\"     from: @(#)vp.4	8.1 (Berkeley) 6/5/93
35.\"
36.Dd June 5, 1993
37.Dt VP 4 vax
38.Os
39.Sh NAME
40.Nm vp
41.Nd Versatec printer/plotter interface
42.Sh SYNOPSIS
43.Cd "vp0 at uba0 csr 0177510 vector vpintr vpintr"
44.Sh DESCRIPTION
45The Versatec printer/plotter is normally used with the
46line printer system.
47This description is designed for those who wish to drive the Versatec directly.
48.Pp
49To use the Versatec yourself, you must realize that you cannot open the
50device,
51.Pa /dev/vp0
52if there is a daemon active.
53You can see if there is a daemon active by doing a
54.Xr lpq 1 ,
55and seeing if there are any files being sent.
56Printing should be turned off using
57.Xr lpc 8 .
58.Pp
59To set the Versatec into plot mode you should include
60.Aq Pa sys/vcmd.h
61and use the
62.Xr ioctl 2
63call
64.Bd -literal -offset indent
65ioctl(fileno(vp), VSETSTATE, plotmd);
66.Ed
67.Pp
68where
69.Em plotmd
70is defined to be
71.Bd -literal -offset indent
72int plotmd[] = { VPLOT, 0, 0 };
73.Ed
74.Pp
75and
76.Em vp
77is the result of a call to
78.Xr fopen 3
79on stdio.
80When you finish using the Versatec in plot mode you should eject paper
81by sending it a
82.Tn EOT
83after putting it back into print mode, i.e. by
84.Bd -literal -offset indent
85int prtmd[] = { VPRINT, 0, 0 };
86\&...
87fflush(vp);
88ioctl(fileno(vp), VSETSTATE, prtmd);
89write(fileno(vp), "\e04", 1);
90.Ed
91.Sh FILES
92.Bl -tag -width /dev/vp0xx -compact
93.It Pa /dev/vp0
94.El
95.Sh DIAGNOSTICS
96The following error numbers are significant at the
97time the device is opened.
98.Bl -tag -width [ENXIO]
99.It Bq Er ENXIO
100The device is already in use.
101.It Bq Er EIO
102The device is offline.
103.El
104.Sh SEE ALSO
105.Xr lpr 1 ,
106.Xr vtroff 1 ,
107.Xr va 4 ,
108.Xr font 5 ,
109.Xr lpd 8
110.Sh HISTORY
111A
112.Nm
113driver appeared in
114.At v7 .
115.Sh BUGS
116The configuration part of the driver assumes that the device is set up to
117vector print mode through 0174 and plot mode through 0200.
118As the configuration program can't be sure
119which vector interrupted at boot time,
120we specify that it has two interrupt vectors,
121and if an interrupt comes through 0200 it is reset to 0174.
122This is safe for devices with one or two vectors at these two addresses.
123Other configurations with 2 vectors may require changes in the driver.
124