'\"macro stdmacro
.if n .pH ddi_dki.start @(#)start	40.5 of 10/10/89
.\" Copyright 1989 AT&T
.de IX
.ie '\\n(.z'' .tm .Index: \\$1 \\$2 \\$3 \\$4 \\$5 \\$6 \\$7 \\$8 \\$9	\\n%
.el \\!.IX \\$1 \\$2 \\$3 \\$4 \\$5 \\$6 \\$7 \\$8 \\$9
..
.nr X
.if \nX=0 .ds x} start D2D "3B2" "DDI" "\&"
.if \nX=1 .ds x} start D2D "3B2" "DDI"
.if \nX=2 .ds x} start D2D "" "\&"
.if \nX=3 .ds x} start "" "" "\&"
.TH \*(x}
.IX "\f4start\fP(D2D)"
.SH NAME
\f4start\f1 \- start access to a device
.SH SYNOPSIS
.nf
.na
\f4void \f2prefix\f4start();\f1
.ad
.fi
.SH DESCRIPTION
The \f4start\f1 routine is called when a computer starts
placing a device into a known state.  At the time this routine is
called, the developer cannot depend on \f4root\f1 being mounted. 
However, the developer can depend on low level system services being
available such as interrupts enabled. 
.P
A \f4start\f1 routine may perform the following types of activities:
.IP
initialize data structures for device access
.IP
allocate buffers for private buffering scheme
.IP
map device into virtual address space
.IP
initialize hardware
(for example, perform a system generation and reset the board)
.IP
initialize the serial device for character drivers
.IP
initialize any static data associated with the driver
.ig
If the number of hardware devices is not in the master
file, use \f4start\f1 to ascertain this count.
This information is determined
from the EDT and is used in the \f4open\f1(D2D)
routine to verify that the device
number argument is correct.
..
.SH SEE ALSO
.na
\f4init\f1(D2DK)
.ad
