ioat(4) [netbsd man page]

IOAT(4) 						   BSD Kernel Interfaces Manual 						   IOAT(4)

NAME

     ioat -- multiplexing serial communications interface

SYNOPSIS

     For 6-port BOCA IOAT66 board:

     ioat0   at isa? port 0x220 irq 5
     com2    at ioat? slave ?
     com3    at ioat? slave ?
     com4    at ioat? slave ?
     com5    at ioat? slave ?
     com6    at ioat? slave ?
     com7    at ioat? slave ?

DESCRIPTION

     The ioat driver provides support for BOCA Research IOAT66 boards that multiplex together up to six EIA RS-232C (CCITT V.28) communications
     interfaces.

     Each ioat device is the master device for up to six com devices.  The kernel configuration specifies these com devices as slave devices of
     the ioat device, as shown in the synopsis.  The slave ID given for each com device determines which bit in the interrupt multiplexing regis-
     ter is tested to find interrupts for that device.	The port specification for the ioat device is used to compute the base addresses for the
     com subdevices. The port for the interrupt multiplexing register is not programmable.

FILES

     /dev/tty??

SEE ALSO

     com(4)

HISTORY

     The ioat driver was adapted from the boca driver by Michael Richardson.

BSD
								 January 24, 2000							       BSD

PTY(4)							   BSD Kernel Interfaces Manual 						    PTY(4)

NAME

     pty -- BSD-style compatibility pseudo-terminal driver

SYNOPSIS

     device pty

DESCRIPTION

     The pty driver provides support for the traditional BSD naming scheme that was used for accessing pseudo-terminals.  When the device
     /dev/ptyXX is being opened, a new terminal shall be created with the pts(4) driver.  A device node for this terminal shall be created, which
     has the name /dev/ttyXX.

     New code should not try to allocate pseudo-terminals using this interface.  It is only provided for compatibility with older C libraries that
     tried to open such devices when posix_openpt(2) was being called.

FILES

     The BSD-style compatibility pseudo-terminal driver uses the following device names:

     /dev/pty[l-sL-S][0-9a-v]  Pseudo-terminal master devices.

     /dev/tty[l-sL-S][0-9a-v]  Pseudo-terminal slave devices.

DIAGNOSTICS

     None.

SEE ALSO

     posix_openpt(2), pts(4), tty(4)

HISTORY

     A pseudo-terminal driver appeared in 4.2BSD.

BUGS

     Unlike previous implementations, the master slave device nodes are destroyed when the PTY becomes unused.	A call to stat(2) on a nonexistent
     master device will already cause a new master device node to be created.  The master device can only be destroyed by opening and closing it.

     The pty driver cannot be unloaded, because it cannot determine if it is being used.

BSD
								  August 20, 2008							       BSD