|This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.|
This function maps a specified bus-relative range of physical addresses or registers onto a system-space virtual range of addresses.
NDIS_STATUS NdisMMapIoSpace( OUT PVOID * VirtualAddress , IN NDIS_HANDLE MiniportAdapterHandle , IN NDIS_PHYSICAL_ADDRESS PhysicalAddress , IN UINT Length );
NDIS_STATUS_SUCCESS indicates success. One of the following values indicates failure:
This function is called by drivers of NICs that have on-board memory or a bank of device registers appearing in the I/O space of the host. For example, the driver of an NIC that uses PI/O calls this function.
A successful call to this function claims hardware resources in the registry for the driver's NIC. Consequently, only MiniportInitializefunctions call this function.
This function sets the variable at VirtualAddressto NULL if it does not return NDIS_STATUS_SUCCESS.
MiniportInitializegets the PhysicalAddressvalue either from the driver's Parametersregistry key or by calling a bus-type-specific Ndis XXXconfiguration function. The specified physical address range must fall within the I/O space of the current platform. It is a programming error to call this function with a host physical memory address.
A miniport must call the reciprocal NdisMUnmapIoSpacefunction to release its claim on system resources if MiniportInitializesubsequently fails to initialize the NIC, if its NIC is removed from the machine, and/or when the driver is unloading.
A driver that calls this function runs at IRQL PASSIVE_LEVEL.
|Runs on||Versions||Defined in||Include||Link to|
|Windows CE OS||2.0 and later||Ndis.h|
Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
Last updated on Tuesday, July 13, 2004