dr(4) [bsd man page]
DR(4) Kernel Interfaces Manual DR(4) NAME
dr - DR11-W general purpose interface driver SYNOPSIS
/sys/conf/SYSTEM: NDR dr11-w_units # DR11-W /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments dr ? 172410 124 5 drintr # dr11-w (b-bus emulator) dr ? 172430 130 5 drintr # dr11-w (gc-bus emulator) dr ? 172450 134 5 drintr # dr11-w (em-2 interface) major device number(s): raw: 12 minor device encoding: bits 0007 specify DR unit DESCRIPTION
The Digital Equipment 1981-82 Peripherals Handbook states the following about the DR11-W: The The DR11-W is a general purpose, direct memory access (DMA) interface to the PDP-11 UNIBUS or VAX UNIBUS. The DR11-W moves data directly between memory and the UNIBUS to and from the user's peripheral. It features: o Word or byte transfers. o Programmed or direct memory access (DMA) block transfers. o Burst data transfers. o User-controlled transfer rates up to memory speed. The DR11-W is a 53-line direct memory access (DMA) interface to the PDP-11 UNIBUS or VAX UBA, which allows the user to control data transfers between the host processor and a peripheral. The DR11-W has 32 data lines (for transferring 16-bit parallel data) and 21 control lines (for transferring control and status information. When used as an interprocessor buffer (IPB), the DR11-W allows data transfers between two processors. Interprocessor communication is accomplished by attaching one DR11-W to each processor UNIBUS or UBA and then cabling the two DR11-Ws together. There. Now you know as much about it as I do. A number of ioctl(2) calls apply to the dr devices, and have the form #include <pdpuba/drreg.h> ioctl(fildes, code, arg) int *arg; The applicable codes are: DRGTTY Get DR11-W status. DRSTTY Set flags and function. DRSFUN Set function. DRSFLAG Set flags. DRGCSR Get CSR and WCR. DRSSIG Set signal for ATTN interrupt. DRESET Reset DR11-W interface. DRSTIME Set timeout. DRCTIME Set timeout inactive. DROUTPUT Put word in output data register. DRINPUT Get word from input data register. DRITIME Don't ignore errors on timeout. FILES
/dev/dr[0-7] device special files /dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
dtab(5), autoconfig(8) DIAGNOSTICS
dr%d: error csr=%b, eir=%b dr%d: timeout error BUGS
This interface is only available under 2.9BSD and 2.11BSD. No documentation exists on how to use it. 3rd Berkeley Distribution January 27, 1996 DR(4)
Check Out this Related Man Page
TM(4) Kernel Interfaces Manual TM(4) NAME
tm - TM-11/TE-10 magtape interface SYNOPSIS
/sys/conf/SYSTEM: # Setting AVIVTM configures the TM driver for the AVIV 800/1600/6250 # controller. For more details, see /sys/pdpuba/tm.c. NTM tm_drives # TM11 AVIVTM YES # AVIV 800/1600/6250 controller /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments tm ? 172520 224 5 tmintr # tm11 driver major device number(s): raw: 7 block: 1 minor device encoding: bits 0003 specify TS drive bit 0004 specifies no-rewind operation bits 0030 specify recording density: 0000: 800BPI 0010: 1600BPI (AVIVTM and some other controllers) 0020: 6250BPI (AVIVTM only) DESCRIPTION
The tm-11/te-10 combination provides a standard tape drive interface as described in mtio(4). The standard DEC tm-11 operates only at 800 bpi. Other controllers of this type may also allow operation at 1600 bpi, under software control or by switching manually. FILES
/dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
mt(1), tar(1), tp(1), mtio(4), ht(4), ts(4), mt(4), dtab(5), autoconfig(8) DIAGNOSTICS
te%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi- nal of the user who tried to access the tape. te%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who tried to access the tape. te%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the tape. This message is written on the terminal of the user who tried to switch the density. te%d: hard error bn%d er=%b. A tape error occurred at block bn; the tm error register is printed in octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation which failed several times before reporting the error. te%d: lost interrupt. A tape operation did not complete within a reasonable time, most likely because the tape was taken off-line during rewind or lost vacuum. The controller should, but does not, give an interrupt in these cases. The device will be made available again after this message, but any current open reference to the device will return an error as the operation in progress aborts. BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed. 3rd Berkeley Distribution January 28, 1988 TM(4)