THIS PAGE IS STILL UNDER DEVELOPMENT!!!!!

NAME

oct − Central Data Octal Serial Interface

SYNOPSIS

device oct0 at mbio

DESCRIPTION

An octal serial interface provides 8 communication lines

Each line attached to the DH-11 communications multiplexer behaves as described in tty(4). Input and output for each line may independently be set to run at any of 16 speeds; see tty(4) for the encoding.

Bit i of flags may be specified for a oct to say that a line is not properly connected, and that the line should be treated as hard-wired with carrier always present.  Thus specifying “flags 0x0004” in the specification of oct0 would cause line ttyh2 to be treated in this way. 

The oct driver norally uses input silos and polls for input at each clock tick (1/60’th of a second) rather than taking an interrupt on each input character. 

FILES

/dev/tty[hi][0-9a-f]
/dev/ttyd[0-9a-f]

SEE ALSO

tty(4)

DIAGNOSTICS

oct%d: silo overflow.  The 64 character input silo overflowed before it could be serviced.  This can happen if a hard error occurs when the CPU is running with elevated priority, as the system will then print a message on the console with interrupts disabled.  If the Berknet net(1) is running on a oct line at high speed (e.g. 9600 baud), there is only 1/15th of a second of buffering capacity in the silo, and overrun is possible.  This may cause a few input characters to be lost to users and a network packet is likely to be corrupted, but the network will recover.  It is not serious. 

Sun System Release 0.3  —  17 February 1983