Configuring SVR5 MDI drivers

Drvmap file convention

All drivers should supply a Drvmap(DSP/4dsp) file for all bus types. netcfg does not actually print the specific string associated with the board ID in the Drvmap file. Instead, netcfg prints the text associated with the NAME parameter in your bcfg(DSP/4dsp) file. This means that the board IDs must be maintained in both the Drvmap file and the BOARD_IDS parameter in the bcfg file. This is because the DCU (Device Configuration Utility) and the HPMUI (HotPlug Manager User Interface) rely on the Drvmap file, while netcfg relies on the bcfg file.

Example wdn Drvmap file

   wdn|Y|Y|Network Interface Cards|SMC/WD 80x3 Family
   |MCA|0x6FC0|WD8003E/A or WD8003ET/A
   |MCA|0x6FC1|WD8003ST/A or WD8003SH/A
   |MCA|0x6FC2|WD8003W/A
   |MCA|0x61C8|SMC8013EP/A
   |MCA|0x61C9|SMC8013WP/A
   |MCA|0xEFE5|IBM Ethernet Adapter/A
   |MCA|0xEFD4|IBM PS/2 Adapter/A for Ethernet TP
   |MCA|0xEFD5|IBM PS/2 Adapter/A for Ethernet
   |ISA||SMC/WD 8003/8013 ISA