Hardware configuration

The paradigm for driver autoconfiguration and autodetection in SVR5 follows the resource manager model established for SCO SVR5 2.0 and is quite different from that used in SCO OpenServer 5. See ``Autoconfiguration'' for information about these facilities.

To summarize:

• The resource manager presents all parameters as strings.

• Hardware configuration is implemented with dcu (Device Configuration Utility), resmgr (resource manager), or a SCOAdmin manager, depending on the type of device being configured. See ``Resource manager database'' and ``Using configuration interfaces''.

• Drivers can view configuration information from the resource manager databsae with the cm_getval(D3) function and the parameters documented on the cm_params(D5) manual page. Note that DDI 8 drivers must only call cm_getval( ) from within a configuration manager transaction, begun with a call to cm_begin_trans(D3) and ended with a call to cm_end_trans(D3).

• View the sample drivers to get an understanding of how driver autoconfiguration works.