Note If you are building a universal or mobile driver package, this directive is not valid. See Using a Universal INF File.
A LogConfig directive references one or more INF-writer-defined sections, each of which specifies a logical configuration of hardware resources − the interrupt request lines, memory ranges, I/O ports, and DMA channels that can be used by the device. Each log-config-section specifies an alternative set of bus-relative hardware resources that can be used by the device.
[DDInstall] | [DDInstall.LogConfigOverride] LogConfig=log-config-section[,log-config-section]...
INF files for non-PnP devices use this directive to create basic configurations.
INF files for PnP devices use this directive only to create override configurations.
Each named section referenced by a LogConfig directive has the following form:
[log-config-section] ConfigPriority=priority-value[,config-type] [DMAConfig=[DMAattrs:]DMANum[,DMANum]...] [IOConfig=io-range[,io-range]...] [MemConfig=mem-range[,mem-range]...] [IRQConfig=[IRQattrs:]IRQNum[,IRQNum]...] [PcCardConfig=ConfigIndex[:[MemoryCardBase1][:MemoryCardBase2]][(attrs)]] [MfCardConfig=ConfigRegBase:ConfigOptions[:IoResourceIndex][(attrs)]...] ...
NORMAL should be specified if the log-config-section was defined in a DDInstall.LogConfigOverride section, and no config-type value can be specified.
DMAattrs is optional if the device is connected on a bus that has only 8-bit DMA channels and the device uses standard system DMA. Otherwise, it can be one of the following letters:
If the device uses bus-master DMA, you must use M with one of the following (mutually exclusive) letters that indicates the type of DMA channel used: A, B, or F. If neither A, B, or F are specified, a standard DMA channel is assumed.
DMANum specifies one or more bus-relative DMA channels as decimal numbers, each separated from the next by a comma (,).
|Mask value||Meaning||IOR_Alias value|
|Mask value||Meaning||IOR_Alias value|
start-end[(attr)] | size@min-max[%align-mask][(attr)]
|C||Combined write allowed|
|D||Card decode addressing is 32-bit, instead of 24-bit|
If both R and W are specified or if neither is specified, read/write is assumed.
If align-mask is omitted, the default memory alignment is on a 4K boundary (FFFFF000).
IRQattrs is omitted if the device uses a bus-relative, edge-triggered IRQ. Otherwise, specify L to indicate a level-triggered IRQ and LS if the device can share the IRQ lines listed in this entry.
IRQNum specifies one or more bus-relative IRQs the device can use as decimal numbers, each separated from the next by a comma (,).
Configures CardBus registers and/or creates up to two permanent memory windows that map to the attribute space of the device. A driver can use the memory windows to access the attribute space from an ISR. Specify all numeric values in hexadecimal format.
The elements of a PcCardConfig entry are as follows:
Optionally specifies one or more attributes for the device, separated by spaces. An invalid attribute specifier invalidates the whole PcCardConfig entry. If more than one specifier for a particular attribute is provided, the attributes are applied to individual I/O or memory windows for the device. If only one specifier is provided, then that attribute is applied to all windows (see the following example).
Specifically, if multiple specifiers are provided, the first specifier found reading from left to right will be applied to the first window, and the next specifier applied to the second window. A maximum of two I/O windows and two memory windows may be controlled by a single PcCardConfig entry. If the device has more than two memory windows, then a second PcCardConfig entry must be included.
The attributes include:
16-bit I/O data path.
The default is 8-bit if the INF specifies a LogConfig directive. If no LogConfig directive is specified, the driver uses 16-bit I/O.
If n is 0, ~IOCS16 is based on the value of the datasize bit. If n is 1, ~IOCS16 is based on the ~IOIS16 signal from the device. The default is S1.
I/O 8-bit, zero wait state.
If n is 1, 8-bit I/O accesses occur with zero additional wait states. If n is 0, access occurs with additional wait states. This flag has no meaning for 16-bit I/O. The default is Z0.
I/O wait states.
If n is 1, 16-bit system accesses occur with one additional wait state. The default is Xl1.
|M||16-bit memory data path. The default is 8-bit.|
|M8||8-bit memory data path.|
Memory wait states, where n can be 0, 1, 2 or 3.
This value determines the number of additional wait states for 16-bit accesses to a memory window. The default is XM3.
|A||Memory range to be mapped as Attribute memory.|
|C||Memory range to be mapped as Common Memory (default).|
For example, an attrs value of (WB CA M XM1 XI0) translates to the following:
1st I/O window is 16-bit
2nd I/O window 8-bit
1st memory window is common
2nd memory window is attribute
Memory is 16-bit
One wait state on memory windows
Zero wait states on I/O windows
MfCardConfig=ConfigRegBase:ConfigOptions[:IoResourceIndex][(attrs)]... Specifies the attribute-memory location of the set of configuration registers for one function of a multifunction device, as follows:
Specifies the index to the IOConfig entry for the bus driver to use in programming the configuration I/O base and limit registers. This index is zero-based, that is, zero designates the initial IOConfig entry in this log-config-section.
Each MfCardConfig entry supplies information about a single function of the multifunction device. When a set of LogConfig directives each reference a discrete log-config-section in the INF's DDInstall.LogConfigOverride section, each log-config-section must have its entries, including MfCardConfig entries, listed in the same order.
An INF for a non-PnP device that supports several alternative logical configurations typically defines a set of log-config-sections under a DDInstall section. Each log-config-section specifies a discrete set of logical configuration resources. It also includes a ConfigPriority entry, which ranks each logical configuration according to its effects on device and driver performance, ease of initialization, and so forth.
For PnP devices, the PnP manager assigns a set of logical hardware resources to each PnP device. That is, the PnP manager queries the system bus drivers, receives their reports of per-device I/O bus configuration resources in use, and assigns per-device sets of logical hardware resources to achieve the best system-wide balance in the usage of all such resources.
As a result, the LogConfig directive under a DDInstall section is ignored for PnP devices,. To override the resources reported by the bus for a PnP device, include the LogConfig directive under a DDInstall.LogConfigOverride section. In this case, the resources specified in the log-config-section is used instead of those reported by the bus.
Platform extensions can be added to a DDInstall section that contains a LogConfig directive, or to a DDInstall.LogConfigOverride section, to specify platform-specific or OS-specific logical configurations. For more information, see Creating an INF File.
A given log-config-section name must be unique to the INF file, but it can be referenced by LogConfig directives in other INF DDInstall sections for the same devices. Each INF-writer-created section name must be unique within the INF file and must follow the general rules for defining section names. For more information about these rules, see General Syntax Rules for INF Files.
Only one ConfigPriority entry can be used in each log-config-section. There can be more than one of each of the other entries, depending on the hardware resource requirements of the device.
One or more MfCardConfig= entries can appear only in a log-config-section that is referenced by a LogConfig directive in the DDInstall.LogConfigOverride section of an INF for a multifunction device. For more information about INF files for multifunction devices, see Supporting Multifunction Devices.
LogConfig-Referenced Section Entries and Values
From a log-config-section, the system installer builds binary logical configuration records and stores them in the registry.
An INF file can contain any number of per-device log-config-sections. However, each such section must contain complete information for installing one device. In general, the INF should specify the entries in each of its log-config-sections in the same order. The INF should specify each set of entries in the order best suited to how the driver initializes its device.
If more than one log-config-section is present for a given device, only one of these INF sections is used during installation. Such an INF file partially controls which such section is used with the ConfigPriority value that it supplies in each such log-config-section. That is, the system installers attempt to honor any configuration priorities in an INF file, but might select a lower ranked logical configuration if a conflict with an already installed device is found.
During installation, one and only one resource from each entry in a given log-config-section is selected and assigned to a particular device. If a particular device needs more than one resource of the same type, a set of entries of that type must be used in its log-config-sections.
For example, to ensure two I/O port ranges for a particular device, two IOConfig= entries must be specified in the log-config-section for that device. On the other hand, if a device requires no IRQ, its INF can omit the IRQConfig entry from the log-config-sections.
This example shows some valid PcCardConfig entries for a PCMCIA device.
PcCardConfig=0:E0000:F0000(W) PcCardConfig=0:E0000(M) PcCardConfig=0::(W) PcCardConfig=0(W)
This example shows a Type 1 I/O range specification in an IOConfig entry. It specifies an I/O port region, eight bytes in size, which can start at 1F8, 2F8, or 3F8.
IOConfig=1F8-1FF, 2F8-2FF, 3F8-3FF
By contrast, this example shows a Type 2 I/O range specification in an IOConfig entry. It specifies an I/O port region, eight bytes in size, which can start at 300, 308, 310, 318, 320, or 328.
This example shows a set of IOConfig entries for a four-port device, each specifying an I/O port range that is offset by 0x400 bytes from the next.
IoConfig=0x200-0x21f IoConfig=0x600-0x61f IoConfig=0xA00-0xA1f IoConfig=0xE00-0xE1f
The next two examples show typical MemConfig entries.
This example specifies a memory region of 32K bytes that can start at either C0000 or D0000.
This example specifies a memory region of 32k bytes starting on 64K boundaries.
This example shows how the system HDC class INF file sets up several log-config-sections for generic ESDI hard disk controllers and uses a DDInstall.LogConfigOverride section for a particular IDE controller.
[MS_HDC] ; per-manufacturer Models section %FujitsuIdePccard.DeviceDesc% = atapi_fujitsu_Inst, PCMCIA\FUJITSU-IDE-PC_CARD-DDF2 %*PNP0600.DeviceDesc% = atapi_Inst, *PNP0600 ; generic ESDI HDCs %PCI\CC_0101.DeviceDesc% = pciide_Inst,,PCI\CC_0101 ; ... other manufacturers' Models sections omitted [atapi_Inst] CopyFiles = @atapi.sys LogConfig = esdilc1, esdilc2, esdilc3, esdilc4 ; ... [atapi_Inst.Services] + service/EventLog-install omitted here [esdilc1] ConfigPriority=HARDWIRED IOConfig=1f0-1f7(3ff::) IoConfig=3f6-3f6(3ff::) IRQConfig=14 [esdilc2] ConfigPriority=HARDWIRED IOConfig=170-177(3ff::) IoConfig=376-376(3ff::) IRQConfig=15 [esdilc3] ConfigPriority=HARDWIRED IOConfig=1e8-1ef(3ff::) IoConfig=3ee-3ee(3ff::) IRQConfig=11 [esdilc4] ; ... [atapi_fujitsu_Inst.LogConfigOverride] LogConfig = fujitsu.LogConfig0 [fujitsu.LogConfig0] ConfigPriority=NORMAL IOConfig=10@100-400%fff0 IRQConfig=14,15,5,7,9,11,12,3 PcCardConfig=1:0:0(W)
For some examples of how MfCardConfig entries are used, see Supporting PC Cards That Have Incomplete Configuration Register Addresses.