1 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
2 .\" All rights reserved.
4 .\" This code is derived from software contributed to Berkeley by
5 .\" the Systems Programming Group of the University of Utah Computer
6 .\" Science Department.
7 .\" Redistribution and use in source and binary forms, with or without
8 .\" modification, are permitted provided that the following conditions
10 .\" 1. Redistributions of source code must retain the above copyright
11 .\" notice, this list of conditions and the following disclaimer.
12 .\" 2. Redistributions in binary form must reproduce the above copyright
13 .\" notice, this list of conditions and the following disclaimer in the
14 .\" documentation and/or other materials provided with the distribution.
15 .\" 3. All advertising materials mentioning features or use of this software
16 .\" must display the following acknowledgement:
17 .\" This product includes software developed by the University of
18 .\" California, Berkeley and its contributors.
19 .\" 4. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" from: @(#)dca.4 5.2 (Berkeley) 3/27/91
36 .\" from: com.4,v 1.1 1993/08/06 11:19:07 cgd Exp
37 .\" from: sio.4,v 1.15 1994/12/06 20:14:30 bde Exp
45 .Nd DigiBoard intelligent serial cards driver
49 This man page was originally written for the dgb driver, and should
50 likely be gone over with a fine tooth comb to reflect differences
53 When not defined the number is computed:
54 .Bd -ragged -offset 4n
57 = number_of_described_DigiBoard_cards * 16
60 If it is less than the actual number of ports
61 the system will be able to use only the
65 If it is greater then all ports will be usable
66 but some memory will be wasted.
70 .Bl -tag -width indent -compact
72 use alternate pinout (exchange DCD and DSR lines)
74 do not use 8K window mode of PC/Xe
79 0b\fICC\fPmmmmmmmm\fIOLIPPPPP\fP
81 \fRmmmmmmmm\fPajor number
90 driver provides support for DigiBoard PC/Xe and PC/Xi series intelligent
91 serial multiport cards with asynchronous interfaces based on the
98 Input and output for each line may set to one of following baud rates;
99 50, 75, 110, 134.5, 150, 300, 600, 1200, 1800, 2400, 4800, 9600,
100 19200, 38400, 57600, or for newer versions of cards 115200.
102 The driver does not use any interrupts, it is
105 it uses clock interrupts instead of interrupts generated by DigiBoard cards and
106 checks the state of cards 25 times per second.
107 This is practical because the
108 DigiBoard cards have large input and output buffers (more than 1Kbyte per
109 port) and hardware that allows efficiently finding the port that needs
111 The only problem seen with this policy is slower
112 SLIP and PPP response.
114 Each line in the kernel configuration file describes one card, not one port
121 keyword may be used on each
123 line in the kernel configuration file
124 to change the pinout of the interface or to use new PC/Xe cards
125 which can work with an 8K memory window in compatibility mode
126 (with a 64K memory window).
128 that using 8K memory window does not mean shorter input/output buffers, it means
129 only that all buffers will be mapped to the same memory address and switched as
134 value must be the same
137 set on the card by jumpers.
138 For PC/Xi cards the same rule is applicable to the
141 It must be the same as the memory address set on the card
143 .\"Some documentation gives the address as a ``paragraph'' or ``segment'';
144 .\"you can get the value of address by adding the digit "0" at end of
145 .\"paragraph value, e.g., 0xfc000 -> 0xfc0000.
146 For PC/Xe cards there is no need to use jumpers for this purpose.
147 In fact there are no jumpers to do it.
149 write the address you want as the
151 value in kernel config file and the card will be programmed
154 The same range of memory addresses may be used
155 for all the DigiBoards installed
156 (but not for any other card or real memory).
158 with a large amount of memory (256K or 512K and perhaps
159 even 128K) must be mapped
160 to memory addresses outside of the first megabyte.
162 has more than 15 megabytes of memory then there is no free address space
163 outside of the first megabyte where such DigiBoards can be mapped.
165 may need to reduce the amount of memory in the computer.
166 But many machines provide a better solution.
167 They have the ability to
169 the memory in the 16th megabyte (addresses 0xF00000 - 0xFFFFFF)
172 Then the DigiBoard's address space can be set to this
174 .\" XXX the following should be true for all serial drivers and
175 .\" should not be repeated in the man pages for all serial drivers.
176 .\" It was copied from sio.4. The only changes were s/sio/dgb/g.
178 Serial ports controlled by the
180 driver can be used for both
184 For each port there is a callin device and a callout device.
185 The minor number of the callout device is 128 higher
186 than that of the corresponding callin port.
187 The callin device is general purpose.
188 Processes opening it normally wait for carrier
189 and for the callout device to become inactive.
190 The callout device is used to steal the port from
191 processes waiting for carrier on the callin device.
192 Processes opening it do not wait for carrier
193 and put any processes waiting for carrier on the callin device into
194 a deeper sleep so that they do not conflict with the callout session.
195 The callout device is abused for handling programs that are supposed
196 to work on general ports and need to open the port without waiting
197 but are too stupid to do so.
201 driver also supports an initial-state and a lock-state control
202 device for each of the callin and the callout
205 The minor number of the initial-state device is 32 higher
206 than that of the corresponding data device.
207 The minor number of the lock-state device is 64 higher
208 than that of the corresponding data device.
209 The termios settings of a data device are copied
210 from those of the corresponding initial-state device
211 on first opens and are not inherited from previous opens.
214 in the normal way on the initial-state devices to program
215 initial termios states suitable for your setup.
217 The lock termios state acts as flags to disable changing
219 E.g., to lock a flag variable such as
222 .Dq Li "stty crtscts"
223 on the lock-state device.
224 Speeds and special characters
225 may be locked by setting the corresponding value in the lock-state
226 device to any nonzero value.
228 Correct programs talking to correctly wired external devices
229 .\" XXX change next line in other man pages too, and rewrite this paragraph.
230 work with almost arbitrary initial states and no locking,
231 but other setups may benefit from changing some of the default
232 initial state and locking the state.
233 In particular, the initial states for non (POSIX) standard flags
234 should be set to suit the devices attached and may need to be
235 locked to prevent buggy programs from changing them.
238 should be locked on for devices that support
239 RTS/CTS handshaking at all times and off for devices that do not
242 should be locked on for devices
243 that do not support carrier.
245 may be locked off if you do not
246 want to hang up for some reason.
247 In general, very bad things happen
248 if something is locked to the wrong state, and things should not
249 be locked for devices that support more than one setting.
252 flag on callin ports should be locked off for logins
253 to avoid certain security holes, but this needs to be done by
254 getty if the callin port is used for anything else.
256 .Bl -tag -width /dev/ttyiD?? -compact
261 corresponding callin initial-state and lock-state devices
267 corresponding callout initial-state and lock-state devices
270 .Bl -tag -width /etc/rc.serial -compact
271 .It Pa /etc/rc.serial
272 examples of setting the initial-state and lock-state devices
275 The first question mark in these device names is short for the
277 (a decimal number between 0 and 65535 inclusive).
278 The second question mark is short for the port number
279 (a letter in the range [0-9a-v]).
281 You may enable extended diagnostics by defining DEBUG at the
282 start of the source file
285 .It dgb\fIX\fP: warning: address \fIN\fP truncated to \fIM\fP
286 The memory address for the PC/Xe's 8K window is misaligned (it should be
287 on an 8K boundary) or outside of the first megabyte.
288 .It dgb\fIX\fP: 1st reset failed
289 Problems with accessing I/O port of the card, probably
292 value is specified in the kernel config file.
293 .It dgb\fIX\fP: 2nd reset failed
294 Problems with hardware.
295 .It dgb\fIX\fP: \fIN\fP[st,nd,rd,th] memory test failed
296 Problems with accessing the memory of the card, probably
299 value is specified in the kernel config file.
300 .It dgb\fIX\fP: BIOS start failed
301 Problems with starting the on-board BIOS.
302 Probably the memory addresses of the
303 DigiBoard overlap with some other device or with RAM.
304 .It dgb\fIX\fP: BIOS download failed
305 Problems with the on-board BIOS.
306 Probably the memory addresses of the
307 DigiBoard overlap with some other device or with RAM.
308 .It dgb\fIX\fP: FEP code download failed
309 Problems with downloading of the Front-End Processor's micro-OS.
310 Probably the memory addresses of the
311 DigiBoard overlap with some other device or with RAM.
312 .It dgb\fIX\fP: FEP/OS start failed
313 Problems with starting of the Front-End Processor's micro-OS.
314 Probably the memory addresses of the
315 DigiBoard overlap with some other device or with RAM.
316 .It dgb\fIX\fP: too many ports
317 This DigiBoard reports that it has more than 32 ports.
318 Perhaps a hardware problem or
319 the memory addresses of the
320 DigiBoard overlap with some other device or with RAM.
321 .It dgb\fIX\fP: only \fIN\fP ports are usable
324 parameter is too small and there is only enough space allocated
328 .It dgb\fIX\fP: port \fIY\fP is broken
329 The on-board diagnostic has reported that the specified port has hardware
331 .It dgb\fIX\fP: polling of disabled board stopped
332 Internal problems in the polling logic of driver.
333 .It dgb\fIX\fP: event queue's head or tail is wrong!
334 Internal problems in the driver or hardware.
335 .It dgb\fIX\fP: port \fIY\fP: got event on nonexisting port
336 Some status changed on a port that is physically present but is
337 unusable due to misconfiguration.
338 .It dgb\fIX\fP: port \fIY\fP: event \fIN\fP mstat \fIM\fP lstat \fIK\fP
339 The driver got a strange event from card.
340 Probably this means that you have a
341 newer card with an extended list of events or some other hardware problem.
342 .It dgb\fIX\fP: port \fIY\fP: overrun
343 Input buffer has filled up.
344 Problems in polling logic of driver.
345 .It dgb\fIX\fP: port \fIY\fP: FEP command on disabled port
346 Internal problems in driver.
347 .It dgb\fIX\fP: port \fIY\fP: timeout on FEP command
348 Problems in hardware.
355 .\" XXX add next line to many other drivers.
359 driver is derived from the
361 driver and the DigiBoard driver from
366 The implementation of sending
370 of fixed length of 1/4 s
373 There was a bug in implementation of
375 It is fixed now but not widely tested yet.
377 There is no ditty command.
378 Most of its functions (alternate pinout,
379 speed up to 115200 baud, etc.) are implemented in the driver itself.
381 other functions are missing.