Print this page
11639 some man pages show incorrect driver locations
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man7d/ecpp.7d
+++ new/usr/src/man/man7d/ecpp.7d
1 1 '\" te
2 2 .\" Copyright (c) 2004, Sun Microsystems, Inc. All Rights Reserved
3 3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 -.TH ECPP 7D "May 13, 2017"
6 +.TH ECPP 7D "Jan 10, 2020"
7 7 .SH NAME
8 8 ecpp \- IEEE 1284 compliant parallel port driver
9 9 .SH SYNOPSIS
10 -.LP
11 10 .nf
12 11 #include <sys/types.h>
13 12 .fi
14 13
15 14 .LP
16 15 .nf
17 16 #include <sys/ecppio.h>
18 17 .fi
19 18
20 19 .LP
21 20 .nf
22 21 ecpp@unit-address
23 22 .fi
24 23
25 24 .SH DESCRIPTION
26 -.LP
27 25 The \fBecpp\fR driver provides a bi-directional interface to \fIIEEE 1284\fR
28 26 compliant devices as well as a forward single-directional interface to
29 27 Centronics devices. In addition to the Centronics protocol, the \fBecpp\fR
30 28 driver supports the \fIIEEE 1284\fRCompatibility, Nibble, and ECP protocols.
31 29 \fBECPP_COMPAT_MODE\fR and \fBECPP_CENTRONICS\fR modes of operation have
32 30 logically identical handshaking protocols, however devices that support
33 31 \fBECPP_COMPAT_MODE\fR are \fIIEEE 1284\fR compliant devices. \fIIEEE 1284\fR
34 32 compliant devices support at least \fBECPP_COMPAT_MODE\fR and
35 33 \fBECPP_NIBBLE_MODE\fR. Centronics devices support only \fBECPP_CENTRONICS\fR
36 34 mode.
37 35 .sp
38 36 .LP
39 37 By default, \fBECPP_COMPAT_MODE\fR devices have a strobe handshaking pulse
40 38 width of 500ns. For this mode, forward data transfers are conducted by DMA. By
|
↓ open down ↓ |
4 lines elided |
↑ open up ↑ |
41 39 default, the strobe pulse width for \fBECPP_CENTRONICS\fR devices is two
42 40 microseconds. Forward transfers for these devices are managed through PIO. The
43 41 default characteristics for both \fBECPP_COMPAT_MODE\fR and
44 42 \fBECPP_CENTRONICS\fR devices may be changed through tunable variables defined
45 43 in \fBecpp.conf\fR.
46 44 .sp
47 45 .LP
48 46 The \fBecpp\fR driver is an \fIexclusive-use\fR device, meaning that if the
49 47 device is already open, subsequent opens fail with \fBEBUSY\fR.
50 48 .SS "Default Operation"
51 -.LP
52 49 Each time the \fBecpp\fR device is opened, the device is marked as \fBEBUSY\fR
53 50 and the configuration variables are set to their default values. The
54 51 \fBwrite_timeout\fR period is set to 90 seconds.
55 52 .sp
56 53 .LP
57 54 The driver sets the mode variable according to the following algorithm: The
58 55 driver initially attempts to negotiate the link into \fBECPP_ECP_MODE\fR during
59 56 \fBopen\fR(2). If it fails, the driver tries to negotiate into
60 57 \fBECPP_NIBBLE_MODE\fR mode. If that fails, the driver operates in
61 58 \fBECPP_CENTRONICS\fR mode. Upon successfully opening the device, \fIIEEE
62 59 1284\fR compliant devices will be left idle in either reverse idle phase of
63 60 \fBECPP_ECP_MODE\fR or in \fBECPP_NIBBLE_MODE\fR. Subsequent calls to
|
↓ open down ↓ |
2 lines elided |
↑ open up ↑ |
64 61 \fBwrite\fR(2) invokes the driver to move the link into either
65 62 \fBECPP_COMPAT_MODE\fR or the forward phase of \fBECPP_ECP_MODE\fR. After the
66 63 transfer completes, the link returns to idle state.
67 64 .sp
68 65 .LP
69 66 The application may attempt to negotiate the device into a specific mode or set
70 67 the \fBwrite_timeout\fR values through the \fBECPPIOC_SETPARMS\fR
71 68 \fBioctl\fR(2) call. For mode negotiation to be successful, both the host
72 69 workstation and the peripheral must support the requested mode.
73 70 .SS "Tunables"
74 -.LP
75 - Characteristics of the \fBecpp\fR driver may be tuned by the variables
71 +Characteristics of the \fBecpp\fR driver may be tuned by the variables
76 72 described in \fB/kernel/drv/ecpp.conf\fR. These variables are read by the
77 73 kernel during system startup. To tune the variables, edit the \fBecpp.conf\fR
78 74 file and invoke \fBupdate_drv\fR(1M) to have the kernel read the file again.
79 75 .sp
80 76 .LP
81 77 Some Centronics peripherals and certain \fIIEEE 1284\fR compatible peripherals
82 78 will not operate with the parallel port operating in a fast handshaking mode.
83 79 If printing problems occur, set "fast-centronics" and "fast-1284-compatible" to
84 80 "false." See \fB/kernel/drv/ecpp.conf\fR for more information.
85 81 .SS "Read/Write Operation"
86 -.LP
87 82 The \fBecpp\fR driver is a full duplex STREAMS device driver. While an
88 83 application is writing to an \fIIEEE 1284\fR compliant device, another thread
89 84 may read from it.
90 85 .SS "Write Operation"
91 -.LP
92 86 A \fBwrite\fR(2) operation returns the number of bytes successfully written to
93 87 the stream head. If a failure occurs while a Centronics device is transferring
94 88 data, the content of the status bits will be captured at the time of the error
95 89 and can be retrieved by the application program using the \fBBPPIOC_GETERR\fR
96 90 \fBioctl\fR(2) call. The captured status information is overwritten each time
97 91 an attempted transfer or a \fBBPPIOC_TESTIO\fR \fBioctl\fR(2) occurs.
98 92 .SS "Read Operation"
99 -.LP
100 93 If a failure or error condition occurs during a \fBread\fR(2), the number of
101 94 bytes successfully read is returned (short read). When attempting to read a
102 95 port that has no data currently available, \fBread\fR(2) returns \fB0\fR if
103 96 \fBO_NDELAY\fR is set. If \fBO_NONBLOCK\fR is set, \fBread\fR(2) returns
104 97 \fB-1\fR and sets errno to \fBEAGAIN.\fR If \fBO_NDELAY\fR and \fBO_NONBLOCK\fR
105 98 are clear, \fBread\fR(2) blocks until data become available.
106 99 .SH IOCTLS
107 -.LP
108 100 The \fBioctl\fR(2) calls described below are supported. Note that when
109 101 \fBecpp\fR is transferring data, the driver waits until the data has been sent
110 102 to the device before processing the \fBioctl\fR(2) call.
111 103 .sp
112 104 .LP
113 105 The ecpp driver supports \fBprnio\fR(7I) interfaces.
114 106 .LP
115 107 Note -
116 108 .sp
117 109 .RS 2
118 110 The \fBPRNIOC_RESET\fR command toggles the \fBnInit\fR signal for 2 ms,
119 111 followed by default negotiation.
120 112 .RE
121 113 .sp
122 114 .LP
123 115 The following \fBioctl\fR(2) calls are supported for backward compatibility and
124 116 are not recommended for new applications:
125 117 .sp
126 118 .ne 2
127 119 .na
128 120 \fB\fBECPPIOC_GETPARMS\fR\fR
129 121 .ad
130 122 .RS 20n
131 123 Get current transfer parameters. The argument is a pointer to a struct
132 124 \fBecpp_transfer_parms\fR. See below for a description of the elements of this
133 125 structure. If no parameters have been configured since the device was opened,
134 126 the structure will be set to its default configuration. See Default Operation
135 127 above for more information.
136 128 .RE
137 129
138 130 .sp
139 131 .ne 2
140 132 .na
141 133 \fB\fBECPPIOC_SETPARMS\fR\fR
142 134 .ad
143 135 .RS 20n
144 136 Set transfer parameters. The argument is a pointer to a struct
145 137 \fBecpp_transfer_parms\fR. If a parameter is out of range, \fBEINVAL\fR is
146 138 returned. If the peripheral or host device cannot support the requested mode,
147 139 \fBEPROTONOSUPPORT\fR is returned. See below for a description of
148 140 \fBecpp_transfer_parms\fR and its valid parameters.
149 141 .sp
150 142 The Transfer Parameters Structure is defined in <\fBsys/ecppio.h\fR>.
151 143 .sp
152 144 .in +2
153 145 .nf
154 146 struct ecpp_transfer_parms {
155 147 int write_timeout;
156 148 int mode;
157 149 };
158 150 .fi
159 151 .in -2
160 152
161 153 The \fBwrite_timeout\fR field is set to the value of
162 154 \fBecpp-transfer-timeout\fR specified in the \fBecpp.conf\fR. The
163 155 \fBwrite_timeout\fR field specifies how long the driver will wait for the
164 156 peripheral to respond to a transfer request. The value must be greater than
165 157 \fB0\fR and less than \fBECPP_MAX_TIMEOUT.\fR All other values are out of
166 158 range.
167 159 .sp
168 160 The mode field reflects the \fIIEEE 1284\fR mode to which the parallel port is
169 161 currently configured. The mode may be set to one of the following values only:
170 162 \fBECPP_CENTRONICS\fR, \fBECPP_COMPAT_MODE\fR, \fBECPP_NIBBLE_MODE\fR,
171 163 \fBECPP_ECP_MODE\fR. All other values are invalid. If the requested mode is not
172 164 supported, \fBECPPIOC_SETPARMS\fR will return \fBEPROTONOSUPPORT\fR and the
173 165 mode will be set to \fBECPP_CENTRONICS\fR mode. Afterwards, the application may
174 166 change the mode back to the original mode with \fBECPPIOC_SETPARMS\fR.
175 167 .RE
176 168
177 169 .sp
178 170 .ne 2
179 171 .na
180 172 \fB\fBECPPIOC_GETDEVID\fR\fR
181 173 .ad
182 174 .RS 20n
183 175 This ioctl gets the \fIIEEE 1284\fR device ID from the peripheral in specified
184 176 mode. Currently, the device ID can be retrieved only in Nibble mode. A pointer
185 177 to the structure defined in \fB<sys/ecppsys.h>\fR must be passed as an
186 178 argument.
187 179 .sp
188 180 The 1284 device ID structure:
189 181 .sp
190 182 .in +2
191 183 .nf
192 184 struct ecpp_device_id {
193 185 int mode; /* mode to use for reading device id */
194 186 int len; /* length of buffer */
195 187 int rlen; /* actual length of device id string */
196 188 char *addr; /* buffer address */
197 189 };
198 190 .fi
199 191 .in -2
200 192
201 193 The mode is the \fIIEEE 1284\fR mode into which the port will be negotiated to
202 194 retrieve device ID information. If the peripheral or host do not support the
203 195 mode, \fBEPROTONOSUPPORT\fR is returned. Applications should set mode to
204 196 \fBECPP_NIBBLE_MODE\fR. \fBlen\fR is the length of the buffer pointed to by
205 197 \fBaddr\fR. \fBrlen\fR is the actual length of the device ID string returned
206 198 from the peripheral. If the returned \fBrlen\fR is greater than \fBlen\fR, the
207 199 application can call \fBECPPIOC_GETDEVID\fR again with a buffer length equal or
208 200 greater than \fBrlen\fR. Note that the two length bytes of the \fIIEEE 1284\fR
209 201 device ID are not taken into account and are not returned in the user buffer.
210 202 .sp
211 203 After \fBECPPIOC_GETDEVID\fR successfully completes, the driver returns the
212 204 link to \fBECPP_COMPAT_MODE\fR. The application is responsible for determining
213 205 the previous mode the link was operating in and returning the link to that
214 206 mode.
215 207 .RE
216 208
217 209 .sp
218 210 .ne 2
219 211 .na
220 212 \fB\fBBPPIOC_TESTIO\fR\fR
221 213 .ad
222 214 .RS 20n
223 215 Tests the forward transfer readiness of a peripheral operating in Centronics or
224 216 Compatibility mode.
225 217 .sp
226 218 \fBTESTIO\fR determines if the peripheral is ready to receive data by checking
227 219 the open flags and the Centronics status signals. If the current mode of the
228 220 device is \fBECPP_NIBBLE_MODE\fR, the driver negotiates the link into
229 221 \fBECPP_COMPAT_MODE\fR, check the status signals and then return the link to
230 222 \fBECPP_NIBBLE_MODE\fR mode. If the current mode is \fBECPP_CENTRONICS\fR or
231 223 \fBECPP_COMPAT_MODE\fR, \fBTESTIO\fR examines the Centronics status signals in
232 224 the current mode. To receive data, the device must have the \fBnErr\fR and
233 225 \fBSelect\fR signals asserted and must not have the \fBPE\fR and \fBBusy\fR
234 226 signals asserted. If \fBecpp\fR is transferring data, \fBTESTIO\fR waits until
235 227 the previous data sent to the driver is delivered before executing
236 228 \fBTESTIO\fR. However if an error condition occurs while a \fBTESTIO\fR is
237 229 waiting, \fBTESTIO\fR returns immediately. If \fBTESTIO\fR determines that the
238 230 conditions are ok, \fB0\fR is returned. Otherwise, \fB-1\fR is returned, errno
239 231 is set to \fBEIO\fR and the state of the status pins is captured. The captured
240 232 status can be retrieved using the \fBBPPIOC_GETERR\fR \fBioctl\fR(2) call. The
241 233 \fBtimeout_occurred\fR and \fBbus_error\fR fields will never be set by this
242 234 \fBioctl\fR(2). \fBBPPIOC_TESTIO\fR and \fBBPPIOC_GETERR\fR are compatible to
243 235 the ioctls specified in \fBbpp\fR(7D).
244 236 .RE
245 237
246 238 .sp
247 239 .ne 2
248 240 .na
249 241 \fB\fBBPPIOC_GETERR\fR\fR
250 242 .ad
251 243 .RS 20n
252 244 Get last error status. The argument is a pointer to a \fBstruct
253 245 bpp_error_status\fR defined in \fB<sys/bpp_io.h>\fR header file. The error
254 246 status structure is:
255 247 .sp
256 248 .in +2
257 249 .nf
258 250 struct bpp_error_status {
259 251 char timeout_occurred; /* 1=timeout */
260 252 char bus_error; /* not used */
261 253 uchar_t pin_status; /* status of pins which
262 254 /* could cause error */
263 255 };
264 256 .fi
265 257 .in -2
266 258
267 259 The pin_status field indicates possible error conditions. The valid bits for
268 260 pin_status are: \fBBPP_ERR_ERR\fR, \fBBPP_SLCT_ERR\fR, \fBBPP_PE_ERR\fR,
269 261 \fBBPP_BUSY_ERR\fR. A set bit indicates that the associated pin is asserted.
270 262 .sp
271 263 This structure indicates the status of all the appropriate status bits at the
272 264 time of the most recent error condition during a \fBwrite\fR(2) call, or the
273 265 status of the bits at the most recent \fBBPPIOC_TESTIO\fR \fBioctl\fR(2)call.
274 266 .sp
275 267 \fBpin_status\fR indicates possible error conditions under
276 268 \fBECPP_CENTRONICS\fR or \fBECPP_COMPAT_MODE\fR. Under these modes, the state
277 269 of the status pins will indicate the state of the device. For instance, many
278 270 Centronics printers lower the \fBnErr\fR signal when a paper jam occurs. The
279 271 behavior of the status pins depends on the device. Additional status
280 272 information may be retrieved through the backchannel.
281 273 .sp
282 274 The \fBtimeout_occurred\fR value is set when a timeout occurs during
283 275 \fBwrite\fR(2). \fBbus_error\fR is not used in this interface.
284 276 .RE
285 277
286 278 .sp
287 279 .LP
288 280 The following ioctls are used to directly read and write the parallel port
289 281 status and control signals. If the current mode of the device is
290 282 \fBECPP_ECP_MODE\fR or \fBECPP_NIBBLE_MODE\fR, the driver negotiates the link
291 283 into \fBECPP_COMPAT_MODE\fR, gets or sets the registers and then returns the
292 284 link to \fBECPP_NIBBLE_MODE\fR. If the current mode is \fBECPP_CENTRONICS\fR or
293 285 \fBECPP_COMPAT_MODE\fR, these ioctls will get/set the register values in the
294 286 current mode.
295 287 .sp
296 288 .ne 2
297 289 .na
298 290 \fB\fBECPPIOC_GETREGS\fR\fR
299 291 .ad
300 292 .RS 19n
301 293 Read register values. The argument is a pointer to a \fBstruct ecpp_regs\fR.
302 294 See below for a description of this structure.
303 295 .RE
304 296
305 297 .sp
306 298 .ne 2
307 299 .na
308 300 \fB\fBECPPIOC_SETREGS\fR\fR
309 301 .ad
310 302 .RS 19n
311 303 Set \fBecpp\fR register values. The argument is a pointer to a \fBstruct
312 304 ecpp_regs\fR. See below for a description of this structure. If a parameter is
313 305 out of range, \fBEINVAL\fR is returned.
314 306 .sp
315 307 The Port Register Structure is defined in <\fBsys/ecppio.h\fR>.
316 308 .sp
317 309 .in +2
318 310 .nf
319 311 struct ecpp_regs {
320 312 uchar dsr; /* status reg */
321 313 u_char dcr; /* control reg */
322 314 };
323 315 .fi
324 316 .in -2
325 317
326 318 The status register is read-only. The \fBECPPIOC_SETREGS\fR ioctl has no affect
327 319 on this register. Valid bit values for dsr are: \fBECPP_nERR\fR,
328 320 \fBECPP_SLCT\fR, \fBECPP_PE\fR, \fBECPP_nACK\fR, \fBECPP_nBUSY\fR. All other
329 321 bits are reserved and always return \fB1\fR.
330 322 .sp
331 323 The control register is read/write. Valid bit values for dcr are:
332 324 \fBECPP_STB\fR, \fBECPP_AFX\fR, \fBECPP_nINIT\fR, \fBECPP_SLCTIN\fR. All other
|
↓ open down ↓ |
215 lines elided |
↑ open up ↑ |
333 325 bits are reserved. Reading reserved bits always return 1. An attempt to write
334 326 0s into these bits results in \fBEINVAL\fR.
335 327 .RE
336 328
337 329 .SH DEVICE SPECIAL FILES
338 330 .ne 2
339 331 .na
340 332 \fB\fB/dev/lp\fIN\fR\fR\fR
341 333 .ad
342 334 .RS 19n
343 -Solaris x86 only. (Backwards compatibility with former \fBlp\fR(7D) devices.)
335 +x86 only. (Backwards compatibility with former \fBlp\fR(7D) devices.)
344 336 .RE
345 337
346 338 .sp
347 339 .ne 2
348 340 .na
349 341 \fB\fB/dev/printers/\fIN\fR\fR\fR
350 342 .ad
351 343 .RS 19n
352 344 1284 compliant parallel port device special files appears in both namespaces.
353 345 .RE
354 346
355 347 .SH FILES
356 348 .ne 2
357 349 .na
358 -\fB\fBkernel/drv/ecpp\fR\fR
350 +\fB/kernel/drv/sparcv9/ecpp\fR
359 351 .ad
360 352 .sp .6
361 353 .RS 4n
362 -32-bit ELF kernel module
354 +Device driver (SPARC)
363 355 .RE
364 356
365 357 .sp
366 358 .ne 2
367 359 .na
368 -\fB\fBkernel/drv/sparcv9/ecpp\fR\fR
360 +\fB/kernel/drv/amd64/ecpp\fR
369 361 .ad
370 362 .sp .6
371 363 .RS 4n
372 -64-bit SPARC ELF kernel module
364 +Device driver (x86)
373 365 .RE
374 366
375 367 .sp
376 368 .ne 2
377 369 .na
378 -\fB\fBkernel/drv/amd64/ecpp\fR\fR
370 +\fB/kernel/drv/ecpp.conf\fR
379 371 .ad
380 372 .sp .6
381 373 .RS 4n
382 -64-bit x86 ELF kernel module
374 +Driver configuration file
383 375 .RE
384 376
385 -.sp
386 -.ne 2
387 -.na
388 -\fB\fBkernel/drv/ecpp.conf\fR\fR
389 -.ad
390 -.sp .6
391 -.RS 4n
392 -driver configuration file
393 -.RE
394 -
395 -.sp
396 -.ne 2
397 -.na
398 -\fB\fBkernel/drv/sparcv9/ecpp.conf\fR\fR
399 -.ad
400 -.sp .6
401 -.RS 4n
402 -driver configuration file for 64-bit SPARC
403 -.RE
404 -
405 -.sp
406 -.ne 2
407 -.na
408 -\fB\fBkernel/drv/amd64/ecpp.conf\fR\fR
409 -.ad
410 -.sp .6
411 -.RS 4n
412 -driver configuration file for 64-bit x86
413 -.RE
414 -
415 377 .SH ERRORS
416 378 .ne 2
417 379 .na
418 380 \fB\fBEBADF\fR\fR
419 381 .ad
420 382 .RS 10n
421 383 The device is opened for write-only access and a read is attempted, or the
422 384 device is opened for read-only access and a write is attempted.
423 385 .RE
424 386
425 387 .sp
426 388 .ne 2
427 389 .na
428 390 \fB\fBEBUSY\fR\fR
429 391 .ad
430 392 .RS 10n
431 393 The device has been opened and another open is attempted. An attempt has been
432 394 made to unload the driver while one of the units is open.
433 395 .RE
434 396
435 397 .sp
436 398 .ne 2
437 399 .na
438 400 \fB\fBEINVAL\fR\fR
439 401 .ad
440 402 .RS 10n
441 403 A \fBECPPIOC_SETPARMS\fR \fBioctl()\fR is attempted with an out-of-range value
442 404 in the \fBecpp_transfer_parms\fR structure. A \fBECPPIOC_SETREGS\fR
443 405 \fBioctl()\fR is attempted with an invalid value in the \fBecpp_regs\fR
444 406 structure. An \fBioctl()\fR is attempted with an invalid value in the command
445 407 argument.An invalid command argument is received during \fBmodload\fR(1M) or
446 408 \fBmodunload\fR(1M).
447 409 .RE
448 410
449 411 .sp
450 412 .ne 2
451 413 .na
452 414 \fB\fBEIO\fR\fR
453 415 .ad
454 416 .RS 10n
455 417 The driver encountered a bus error when attempting an access. A read or write
456 418 did not complete properly, due to a peripheral error or a transfer timeout.
457 419 .RE
458 420
459 421 .sp
460 422 .ne 2
|
↓ open down ↓ |
36 lines elided |
↑ open up ↑ |
461 423 .na
462 424 \fB\fBENXIO\fR\fR
463 425 .ad
464 426 .RS 10n
465 427 The driver has received an open request for a unit for which the attach failed.
466 428 The driver has received a write request for a unit which has an active
467 429 peripheral error.
468 430 .RE
469 431
470 432 .SH ATTRIBUTES
471 -.LP
472 433 See \fBattributes\fR(5) for descriptions of the following attributes:
473 434 .sp
474 435
475 436 .sp
476 437 .TS
477 438 box;
478 439 c | c
479 440 l | l .
480 441 ATTRIBUTE TYPE ATTRIBUTE VALUE
481 442 _
482 443 Architecture PCI-based systems
483 444 _
484 445 ISA-based systems (x86)
485 446 _
486 447 Interface stability Evolving
487 448 .TE
488 449
489 450 .SH SEE ALSO
490 -.LP
491 451 \fBmodload\fR(1M), \fBmodunload\fR(1M), \fBupdate_drv\fR(1M), \fBioctl\fR(2),
492 452 \fBopen\fR(2), \fBread\fR(2), \fBwrite\fR(2), \fBattributes\fR(5),
493 453 \fBbpp\fR(7D), \fBusbprn\fR(7D), \fBprnio\fR(7I), \fBstreamio\fR(7I)
494 454 .sp
495 455 .LP
496 456 \fIIEEE Std 1284-1994\fR
497 457 .SH DIAGNOSTICS
498 458 .ne 2
499 459 .na
500 460 \fBParallel port controller not supported\fR
501 461 .ad
502 462 .sp .6
503 463 .RS 4n
504 464 Driver does not support parallel port controller on the given host. Attach
505 465 failed.
506 466 .RE
507 467
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX