Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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)

See Also
       tty(4), MAKEDEV(8), dmbsp(4)

																	    dmb(4)

Check Out this Related Man Page

cxy(4)							     Kernel Interfaces Manual							    cxy(4)

Name
       cxy - CXY08 communications interface

Syntax
       device dhu0 at uba0 csr 0160440 flags 0x?? vector dhurint dhuxint

Description
       A  CXY08 provides eight communication lines with modem control adequate for UNIX dialup use. The device behaves and looks just like a DHV11
       and is specified in the configuration line the same as a DHV11 device.  Each line attached to the CXY08 communications interface behaves as
       described in and can be set to run at any of 16 speeds. See for the encoding.

       Bit  i of flags can be specified for a device to say that a line is not properly connected and that the line should be treated as hardwired
       with carrier always present.  Thus, specifying flags 0x04 in the specification of would cause line tty02 to be treated in this way.

       The driver normally interrupts on each input character.	The and devices operate under the control of the driver.

Diagnostics
       dhu%d: receive fifo overflow
       The character input fifo overflowed before it could be serviced.  This can happen if a hard error occurs when the CPU is running with  ele-
       vated  priority,  as the system then prints a message on the console with interrupts disabled.  This can cause a few input characters to be
       lost to users.  It is not serious.

       dhu%d:%d DMA ERROR
       A DMA transfer error has occurred.  The unit number and line number are printed.  This means that  the  channel	indicated  has	failed	to
       transfer  DMA data within 10.7 microseconds of the bus request being acknowledged or that there is a memory parity error.  This may cause a
       few output characters to be lost.

       dhu%d: DIAG. FAILURE
       This indicates that the internal diagnostics have detected an error.

       dhu%d: DHU 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.

Files
       Dialups

See Also
       tty(4), MAKEDEV(8)

																	    cxy(4)
Man Page