Autoconfiguration (or ``autoconfig'')
refers to hardware configuration
that is performed under software control,
and with limited user-provided information.
Autodetection (or ``autodetect'')
refers to software that detects
the existence and characteristics of specific hardware.
DDI autoconfiguration is implemented with the following:
User application used to view and,
in some cases, modify driver and system configuration.
Interface between device drivers and
the resource manager database. See
An incore kernel module
that serves as a repository for information
about hardware and drivers that are configured
into the system. See
``Resource manager database''.
The resource manager database is also used
to populate the driver.dat file
that ScoAdmin uses to access device information.
Driver information files that contain information
required by the autoconfiguration facility.
Network adapter driver information files
that provide an interface between
the system autoconfiguration facilities
drivers supplement the standard
DDI autoconfiguration facilities
for managing the configuration of
SDI controllers and devices:
Stores configuration information about
each instance of a target device
supported by the HBA driver.
Allocate array of
Structures that store information about
the device configuration for SDI devices.
Much of this information is accessed
through macros and functions that are referenced
from this manual page.
ODDI autoconfiguration is implemented in the
entry point routine
with the following:
extract bus type from architecture;
used for ISA, EISA,
and MCA architectures
determine the presence of a PCI bus
Print actual configuration information
Drivers can also use the
entry point routine to support the
Device Query Interface (DQI)
that is used by ScoAdmin; see
for more information.
For information about dynamic interrupt registration, see
``Interrupt handlers, attaching and registering''.
© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005