#$version 1 #MANIFEST: FILES="all DSP files used by this driver continuation of list" [EXTRA_FILES="all non-DSP files used by this driver continuation of list"] [CONFIG_CMDS="cmd1 cmd2"] [PRE_SCRIPT=preinstall_script_name] [POST_SCRIPT=postinstall_script_name] #DRIVER: TYPE=DLPI|ODI|MDI FAILOVER=true|false PROMISCUOUS=true|false DRIVER_NAME=name HELPFILE=name [WRITEFW=true|false] [UNIT=number_of_configured_cards] REBOOT=true|false RM_ON_FAILURE="value1 value2" NAME=value1 value2 . . . valuen [CUSTOM_NUM=number_of_custom_specs] [CUSTOM[1]='values contents'] [CUSTOM[2]='values contents'] AUTOCONF=true|false [ISAVERIFY="param1 param2 ... paramn "] [IDTUNE_NUM=number_of_ODI_tunables_specified] [IDTUNE_ARRAY[n ="ODI_parameter_name, value"] [DEPEND=value] #ADAPTER MAX_BD=highest_supported_adapter_number BOARD_IDS=values CONFORMANCE=hex_value [NET_BOOT=static|dynamic|autosearch] ACTUAL_RECEIVE_SPEED=speed ACTUAL_SEND_SPEED=values [DMA="values"] [INT="values"] BUS=bus [MEM="values"] NUM_PORTS=max_number_of_ports_on_board [PORT="values"] TOPOLOGY="ETHER | TOKEN | ISDN | ISDN | FDDI | ATM | X25 | FRAMERELAY | OTHER"
Use the ndcfg(1M) command to check the sanity of the bcfg file. It is also useful to check the /tmp/ncfgLog file that is created when a driver is installed with either the Network Configuration Manager or the -L option to the netcfg(1M) command.
The format of the bcfg file is:
PARAM = "val1 val2"
NAME= "My Acme Driver"
After the user supplies this information, netcfg(1M) changes the IRQ from 2 to 9 and adds the values of UNIT, IRQ, IOADDR, MEMADDR, and DMAC to the particular resource manager key.
IDTUNE_NUM=5 IDTUNE_ARRAY[1]="LSL_1KCHUNKCS, 8" IDTUNE_ARRAY[2]="LSL_2KCHUNKCS, 2" IDTUNE_ARRAY[3]="LSL_6KCHUNKCS, 16" IDTUNE_ARRAY[4]="LSL_10KCHUNKCS, 0" IDTUNE_ARRAY[5]="LSL_36KCHUNKCS, 1"netcfg only allows one driver that specifies values for tunable parameters to be installed at a time, to avoid the problems of having multiple drivers specify values for these paramters. This variable is used only for ODI token ring drivers.
The value of the TYPE= variable determines which drivers are automatically installed by the interface, and so do not need to be listed as a value for the DEPEND= variable. The drivers automatically installed are:
TYPE=MDI | idinstall dlpi, dlipbase, and netX |
TYPE=DLPI | none |
TYPE=ODI | idinstall odimem, net, lsl, and msm modules |
Default value is false.
Set to false for all loadable drivers.
To solicit free-form input from the user, populate this field with:
__string__The user input must be one word with no spaces, maximum 10 characters.
The CUSTOM[xx] variable is used by netinstall when the value is added to the resource manager database. If netcfg is run in silent mode, these values are not filled in, so the driver should define a reasonable default case and print a cmn_err(D3) CE_NOTE message if the parameter is not found in the resource manager database. This is especially true when Line 7 is set to ADVANCED and for mixed topology custom parameters.
WRITEIOADDR READIOADDR WRITEIRQ READIRQ WRITEMEMADDR READMEMADDR WRITEDMA READDMASee ``ISA bus autoconfiguration''.
EISA board IDs are in uncompressed form.
MCA board IDs are the form 0xDDDD where each D is a hexacecimal digit (0-9 or A-F). MCA board IDs must be four digits; use leading zeroes to pad if necessary. So 0x0ABC is correct; 0xABC is not.
PCI board IDs are in the form 0xVVVVDDDD where VVVV is the hexadecimal vendor ID and DDDD is the hexadecimal device ID. Note the lowercase ``x''.
PCI and MCA boards have a specific syntax. Wildcards cannot be used in bcfg files as they are in Drvmap files. Mixed-platform BOARD_IDS are not allowed; all IDs given must be correct for the single specified BUS= line and match the Drvmap file. Create multiple bcfg files, one for each BUS that the driver supports, with the appropriate BOARD_IDS for each BUS in the bcfg file.
Board revisions are not applicable for PCI devices.
If BUS= is PCI, EISA, or MCA, BOARD_IDS must be set unless AUTOCONF=false. In this case, you must also supply ISA parameters or set BUS=ISA and emulate an ISA board.
Interface | Value | Notes |
MDI 2.0 | 0x0200 | see MDI_VERSION in mdi.h header file |
DLPI | 0x02 | see DL_CURRENT_VERSION in dlpi.h header file |
ODI 1.1 | 0x0110 | The SCO UnixWare 2.0 transmogrifier sets 3.2 |
ODI 3.1 | 0x0310 | in the Master file. |
ODI 3.2 | 0x0420 |
The MAC_INFO_ACK(D7mdi) primitive captures this information and passes it to the DL_GET_STATISTICS_REQ(D7dlpi) primitive. This variable provides some measure of performance of a particular card/driver combination to protocol stacks that choose to access it.
This variable provides some measure of performance of a particular card/driver combination to protocol stacks that choose to access it. It does not reflect the speed of the underlying media that is available to stacks as part of a returned DL_GET_STATISTICS_ACK(D7dlpi) primitive. The MAC_INFO_ACK(D7mdi) primitive captures this information and passes it to the DL_GET_STATISTICS_REQ(D7dlpi) primitive.
INT="2 3 4 5 6 9"Drivers that use IRQ 2 should include both 2 and 9 in this parameter list for user convenience, even though ndcfg(1M) silently converts IRQ 2 to IRQ 9 so that only IRQ 9 will really be read.
This variable is not used for autoconfigured drivers.
If BUS= is set to PCCARD, AUTOCONF=false must also be set. Certain EISA boards have this requirement.
This variable limits the selections that the user sees. Users will only be able to select the bcfg file(s) for bus types that are cofigured on the machine.
MEM="start1-end2 start2-end2"Memory addresses are displayed in uppercase hexadecimal notation, without a leading 0x. For example:
MEM="D0000-D1FFF D2000-D3FFF"This variable is not required for autoconfigurable drivers.
PORT="start1-end2 start2-end2"I/O addresses are displayed in uppercase hexadecimal notation, without a leading 0x. For example:
PORT="3FA-3FF 3BC-3EF"This variable is not required for autoconfigurable drivers.
``Network driver packaging and configuration''
``DSP (Driver Software Package)''