dmb(4) [ultrix man page]

dmb(4) Kernel Interfaces Manual dmb(4)

Name
dmb - DMB32 communications multiplexor

Syntax
device dmb0 at vaxbi? node? flags 0x????
vector dmbsint dmbaint dmblint

Description
A DMB32 device provides eight asynchronous communication lines with modem control. The device driver also supports a connection to a line
printer through the line printer port of the DMB32.

Each line attached to a DMB32 serial line port behaves as described in Input and output for each line may independently be set to run at
any of 16 speeds. See for the encoding.

Bit i of flags can be specified for a to say that a line should be treated as a hardwired connection, with carrier always present. If bit
i of flags is not set, the line operates under full modem control. Modem lines will operate in accordance to the CD (carrier detect), DSR
(data set ready) and CTS (clear to send) leads. Thus, specifying ``flags 0x0004'' in the specification of would cause line 2 on the DMB32
to be treated as hardwired, with carrier always present. In this example, the remainder of the lines will be modem control lines.

Restrictions
The DMB32 provides a synchronous port, but this is not supported by the driver.

Diagnostics
dmbinit: async lines unavailable
This message is produced at system boot time, if the DMB32 fails its internal self test, indicating that the asynchronous lines have failed
to configure.

dmbinit: printer port unavailable
This message is produced at system boot time, if the DMB32 fails its internal self test, indicating that the printer port failed to config-
ure.

dmb%d: fifo overflow
The character input fifo overflowed before it could be serviced. This can happen if the CPU is running with elevated priority for too long
a period of time. Overflow errors can indicate that configuration constraints have been reached.

dmb%d: DMA Error. tbuf = 0x%x
A DMA output transfer failed. This can be caused by a memory error or an invalid pte (page table entry). For a description of the error
code in the ``tbuf'' register, see the DMB32 documentation.

dmb%d: DMB Hardware Error. TX.DMA.START failed
The failed to clear the start bit. Normally, this is cleared to signal that a DMA transfer has completed.

dmb%d: Modem Error. tbuf = 0x%x
Indicates a problem with a modem or its cable. For a description of the error code in the ``tbuf'' register, see the DMB32 documentation.

dmb%d: Internal Error. tbuf = 0x%x
Indicates that the DMB32 detected an internal error. For a description of the error code in the ``tbuf'' register, see the DMB32 documen-
tation.

hfBdmb%d: uio move error
An error occurred when copying a printer buffer from user space to system space.

dmbsint
The unsupported synchronous port of the DMB32 interrupted because of a problem. Check your interrupt vectors for a conflict with another
device.

Files
(modem lines only)

Check Out this Related Man Page

DH(4)							     Kernel Interfaces Manual							     DH(4)

NAME

       dh - DH-11/DM-11 communications multiplexer

SYNOPSIS

       /sys/conf/SYSTEM:
	    NDH  dh_units  # DH11; NDH is in units of boards (16 each)
	    NDM  dm_units  # DM11; NDM is in units of boards (16 each)

       /etc/dtab:
	    #Name Unit# Addr   Vector Br Handler(s)	 # Comments
	    dm	  ?	170500 310    4  dmintr 	 # dm11 dh modem control
	    dh	  ?	160020 320    5  dhrint  dhxint  # dh11 terminal mux

       major device number(s):
	    raw: 3
       minor device encoding:
	    bits 0017 specify line on DH unit
	    bits 0060 specify DH unit
	    bit  0100 specify RTS/CTS (``hardware'') flowcontrol
	    bit  0200 specifies non-blocking open (``CD always on'')

DESCRIPTION

       A  dh-11  provides  16 communication lines; dm-11's may be optionally paired with dh-11's to provide modem control for the lines.  If there
       are fewer dm-11's than dh-11's, the dm-11's are assumed to be paired with the first dm_units dh-11's.

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

       Bit  0200  of  the  minor  device  number for DH lines may be set to say that a line is not properly connected, and that the line should be
       treated as hard-wired with carrier always present.  Thus creating the special character device node "3, 130" via mknod /dev/ttyh2 c  3  130
       would cause line ttyh2 to be treated in this way.  Bit 0100 of the minor device number enables RTS/CTS (also called ``hardware'') flow con-
       trol. It is enabled by adding 64 to the minor device number: mknod /dev/ttyh2 c 3 194

       The dh driver monitors the rate of input on each board, and switches between the use of character-at-a-time  interrupts	and  input  silos.
       While the silo is enabled during periods of high-speed input, the driver polls for input 30 times per second.

FILES

       /dev/tty[h-k][0-9a-f]
       /dev/ttyd[0-9a-f]
       /dev/MAKEDEV	   script to create special files
       /dev/MAKEDEV.local  script to localize special files

SEE ALSO

       tty(4), dtab(5), autoconfig(8)

DIAGNOSTICS

       dh%d  NXM.  No response from UNIBUS on a dma transfer within a timeout period.  This has never been observed on a PDP-11 and is a carryover
       from the VAX driver when it was ported.	It is not serious.

       dh%d %d overruns.  The character input silo overflowed before it could be serviced.  This message is only printed at line close	time.	It
       is not serious but does indicate that the system was not able to keep up with the data flow.

3rd Berkeley Distribution					   May 31, 1997 							     DH(4)

Linux and UNIX Man Pages

dmb(4) [ultrix man page]

Check Out this Related Man Page