1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
<table class="head">
<tr>
<td class="head-ltitle">PS(4)</td>
<td class="head-vol">Device Drivers Manual (vax)</td>
<td class="head-rtitle">PS(4)</td>
</tr>
</table>
<div class="manual-text">
<section class="Sh">
<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1>
<p class="Pp"><code class="Nm">ps</code> — <span class="Nd">Evans and
Sutherland Picture System 2 graphics device interface</span></p>
</section>
<section class="Sh">
<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1>
<p class="Pp"><code class="Cd">ps0 at uba? csr 0172460 vector psclockintr
pssystemintr</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">NOTE: This driver has not been ported from
<span class="Ux">4.4BSD</span> yet.</p>
<p class="Pp">The <code class="Nm">ps</code> driver provides access to an Evans
and Sutherland Picture System 2 graphics device. Each minor device is a new
PS2. When the device is opened, its interface registers are mapped, via
virtual memory, into a user process's address space. This allows the user
process very high bandwidth to the device with no system call overhead.</p>
<p class="Pp">DMA to and from the PS2 is not supported. All read and write
system calls will fail. All data is moved to and from the PS2 via programmed
I/O using the device's interface registers.</p>
<p class="Pp">Commands are fed to and from the driver using the following
<a class="Xr">ioctl(2)</a>s:</p>
<dl class="Bl-tag">
<dt id="PSIOGETADDR"><a class="permalink" href="#PSIOGETADDR"><code class="Dv">PSIOGETADDR</code></a></dt>
<dd>Returns the virtual address through which the user process can access the
device's interface registers.</dd>
<dt id="PSIOAUTOREFRESH"><a class="permalink" href="#PSIOAUTOREFRESH"><code class="Dv">PSIOAUTOREFRESH</code></a></dt>
<dd>Start auto refreshing the screen. The argument is an address in user space
where the following data resides. The first longword is a
<i class="Em">count</i> of the number of static refresh buffers. The next
<i class="Em">count</i> longwords are the addresses in refresh memory
where the refresh buffers lie. The driver will cycle through these refresh
buffers displaying them one by one on the screen.</dd>
<dt id="PSIOAUTOMAP"><a class="permalink" href="#PSIOAUTOMAP"><code class="Dv">PSIOAUTOMAP</code></a></dt>
<dd>Start automatically passing the display file through the matrix processor
and into the refresh buffer. The argument is an address in user memory
where the following data resides. The first longword is a
<i class="Em">count</i> of the number of display files to operate on. The
next <i class="Em">count</i> longwords are the address of these display
files. The final longword is the address in refresh buffer memory where
transformed coordinates are to be placed if the driver is not in double
buffer mode (see below).</dd>
<dt id="PSIODOUBLEBUFFER"><a class="permalink" href="#PSIODOUBLEBUFFER"><code class="Dv">PSIODOUBLEBUFFER</code></a></dt>
<dd>Cause the driver to double buffer the output from the map that is going to
the refresh buffer. The argument is again a user space address where the
real arguments are stored. The first argument is the starting address of
refresh memory where the two double buffers are located. The second
argument is the length of each double buffer. The refresh mechanism
displays the current double buffer, in addition to its static refresh
lists, when in double buffer mode.</dd>
<dt id="PSIOSINGLEREFRESH"><a class="permalink" href="#PSIOSINGLEREFRESH"><code class="Dv">PSIOSINGLEREFRESH</code></a></dt>
<dd>Single step the refresh process. That is, the driver does not continually
refresh the screen.</dd>
<dt id="PSIOSINGLEMAP"><a class="permalink" href="#PSIOSINGLEMAP"><code class="Dv">PSIOSINGLEMAP</code></a></dt>
<dd>Single step the matrix process. The driver does not automatically feed
display files through the matrix unit.</dd>
<dt id="PSIOSINGLEBUFFER"><a class="permalink" href="#PSIOSINGLEBUFFER"><code class="Dv">PSIOSINGLEBUFFER</code></a></dt>
<dd>Turn off double buffering.</dd>
<dt id="PSIOTIMEREFRESH"><a class="permalink" href="#PSIOTIMEREFRESH"><code class="Dv">PSIOTIMEREFRESH</code></a></dt>
<dd>The argument is a count of the number of refresh interrupts to take before
turning off the screen. This is used to do time exposures.</dd>
<dt id="PSIOWAITREFRESH"><a class="permalink" href="#PSIOWAITREFRESH"><code class="Dv">PSIOWAITREFRESH</code></a></dt>
<dd>Suspend the user process until a refresh interrupt has occurred. If in
<code class="Dv">TIMEREFRESH</code> mode, suspend until count refreshes
have occurred.</dd>
<dt id="PSIOSTOPREFRESH"><a class="permalink" href="#PSIOSTOPREFRESH"><code class="Dv">PSIOSTOPREFRESH</code></a></dt>
<dd>Wait for the next refresh, stop all refreshes, and then return to user
process.</dd>
<dt id="PSIOWAITMAP"><a class="permalink" href="#PSIOWAITMAP"><code class="Dv">PSIOWAITMAP</code></a></dt>
<dd>Wait until a map done interrupt has occurred.</dd>
<dt id="PSIOSTOPMAP"><a class="permalink" href="#PSIOSTOPMAP"><code class="Dv">PSIOSTOPMAP</code></a></dt>
<dd>Wait for a map done interrupt, do not restart the map, and then return to
the user.</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="FILES"><a class="permalink" href="#FILES">FILES</a></h1>
<dl class="Bl-tag">
<dt><span class="Pa">/dev/ps</span></dt>
<dd style="width: auto;"> </dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
<dt>ps device intr.</dt>
<dd></dd>
<dt>ps DMA intr.</dt>
<dd>An interrupt was received from the device. This shouldn't happen, check
your device configuration for overlapping interrupt vectors.</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp">The <code class="Nm">ps</code> driver appeared in
<span class="Ux">4.2BSD</span>.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1>
<p class="Pp">An invalid access (e.g., longword) to a mapped interface register
can cause the system to crash with a machine check. A user process could
possibly cause infinite interrupts hence bringing things to a crawl.</p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">June 5, 1993</td>
<td class="foot-os">NetBSD 10.1</td>
</tr>
</table>
|
