Autoconfiguration

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 implementation

DDI autoconfiguration is implemented with the following:

dcu(1M)

User application used to view and, in some cases, modify driver and system configuration.

Configuration manager

Interface between device drivers and the resource manager database. See ``Configuration manager''.

Resource manager

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.

Drvmap(DSP/4dsp) files

Driver information files that contain information required by the autoconfiguration facility.

bcfg(DSP/4dsp) files

Network adapter driver information files that provide an interface between the system autoconfiguration facilities and the netcfg configuration utility.

SDI implementation

``SDI''SDI drivers supplement the standard DDI autoconfiguration facilities for managing the configuration of SDI controllers and devices:

hba_idata_v5(D4sdi)

Stores configuration information about each instance of a target device supported by the HBA driver.

sdi_hba_autoconf(D3sdi)

Allocate array of hba_idata_v5(D4sdi) structures.

scsi_ad(D4sdi)

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 implementation

ODDI autoconfiguration is implemented in the init(D2oddi) entry point routine with the following:

archtobus(D3oddi)

extract bus type from architecture; used for ISA, EISA, and MCA architectures

pci_buspresent(D3oddi)

determine the presence of a PCI bus

printcfg(D3oddi)

Print actual configuration information during initialization

Drivers can also use the probe(D2oddi) entry point routine to support the Device Query Interface (DQI) that is used by ScoAdmin; see ``DQI'' for more information.

For information about dynamic interrupt registration, see ``Interrupt handlers, attaching and registering''.