Annotated edit history of
plipconfig(8) version 2, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
PLIPCONFIG |
| |
|
2 |
!!!PLIPCONFIG |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
OPTIONS |
| |
|
7 |
NOTE |
| |
|
8 |
SEE ALSO |
| |
|
9 |
BUGS |
| |
|
10 |
AUTHOR |
| |
|
11 |
---- |
| |
|
12 |
!!NAME |
| |
|
13 |
|
| |
|
14 |
|
| |
|
15 |
plipconfig - fine tune PLIP device parameters |
| |
|
16 |
!!SYNOPSIS |
| |
|
17 |
|
| |
|
18 |
|
| 2 |
JohnMcPherson |
19 |
__plipconfig interface__ |
| |
|
20 |
|
| |
|
21 |
__plipconfig interface ~[nibble NN] ~[trigger NN] ~[unit NN]__ |
| |
|
22 |
|
| 1 |
perry |
23 |
!!DESCRIPTION |
| |
|
24 |
|
| |
|
25 |
|
| |
|
26 |
__Plipconfig__ is used to (hopefully) improve PLIP |
| |
|
27 |
performance by changing the default timing parameters used |
| |
|
28 |
by the PLIP protocol. Results are dependent on the parallel |
| |
|
29 |
port hardware, cable, and the CPU speed of each machine on |
| |
|
30 |
each end of the PLIP link. |
| |
|
31 |
|
| |
|
32 |
|
| |
|
33 |
If the single __interface__ argument is given, |
| |
|
34 |
__plipconfig__ displays the status of the given interface |
| |
|
35 |
only. Otherwise, it will try to set the |
| |
|
36 |
options. |
| |
|
37 |
!!OPTIONS |
| |
|
38 |
|
| |
|
39 |
|
| |
|
40 |
__nibble NN__ |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
Sets the nibble wait value in microseconds. Default is |
| |
|
44 |
3000. |
| |
|
45 |
|
| |
|
46 |
|
| |
|
47 |
__trigger NN__ |
| |
|
48 |
|
| |
|
49 |
|
| |
|
50 |
Sets the trigger wait value in microseconds. Default is |
| |
|
51 |
500. |
| |
|
52 |
|
| |
|
53 |
|
| |
|
54 |
PLIP speed can in some cases be improved by lowering the |
| |
|
55 |
default values. Values which are too low may cause excess |
| |
|
56 |
use of CPU, poor interrupt response time resulting in serial |
| |
|
57 |
ports dropping characters, or in dropping of PLIP packets. |
| |
|
58 |
Changing the plip MTU can also affect PLIP |
| |
|
59 |
speed. |
| |
|
60 |
!!NOTE |
| |
|
61 |
|
| |
|
62 |
|
| |
|
63 |
If you get no response it is far more likely the irq is |
| |
|
64 |
wrong and needs setting with ifconfig. The few cases where |
| |
|
65 |
the default parameters will be too fast are those using very |
| |
|
66 |
long cables. Something you should never do as the parallel |
| |
|
67 |
port is not specified or designed for driving long cable |
| |
|
68 |
runs. |
| |
|
69 |
!!SEE ALSO |
| |
|
70 |
|
| |
|
71 |
|
| |
|
72 |
''ifconfig(8)'' |
| |
|
73 |
!!BUGS |
| |
|
74 |
|
| |
|
75 |
|
| |
|
76 |
Non. |
| |
|
77 |
!!AUTHOR |
| |
|
78 |
|
| |
|
79 |
|
| |
|
80 |
John Paul Morrison, |
| |
|
81 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
