DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Installing, configuring, and packaging SVR5 drivers

Autoconfiguration and advanced bus hardware

Drivers for devices that run on buses supporting autoconfiguration (such as PCI,EISA, and MCA) need to have a mapping between board ID and device driver set up. Normally, the system sets up this mapping during system boot. Frequently, a hardware configuration utility of some kind is also used on these advanced hardware bus-design systems.

However, for the autoconfigurable driver to install correctly, the board ID mapping needs to be done in the driver's postinstall script. This is done by calling dcu -S (or, for MDI drivers, netcfg) in the postinstall script, although it will happen when the system is rebooted. This should be done after the idinstall.


NOTE: Smart-bus (PCI/EISA/MCA) devices can have multiple memory addresses or I/O addresses. If your hardware does this, you should perform a cm_getval(D3) for CM_MEMADDR or CM_IOADDR with ascending cm_n values. See cm_args(D4) for more information.


© 2005 The SCO Group, Inc. All rights reserved.
OpenServer 6 and UnixWare (SVR5) HDK - June 2005