7f3cc43211
and ndis_halt_nic(). It's been disabled for some time anyway, and it turns out there's a possible deadlock in NdisMInitializeTimer() when acquiring the miniport block lock to modify the timer list: it's possible for a driver to call NdisMInitializeTimer() when the miniport block lock has already been acquired by an earlier piece of code. You can't acquire the same spinlock twice, so this can deadlock. Also, implement MmMapIoSpace() and MmUnmapIoSpace(), and make NdisMMapIoSpace() and NdisMUnmapIoSpace() use them. There are some drivers that want MmMapIoSpace() and MmUnmapIoSpace() so that they can map arbitrary register spaces not directly associated with their device resources. For example, there's an Atheros driver for a miniPci card (0x168C:0x1014) on the IBM Thinkpad x40 that wants to map some I/O spaces at 0xF00000 and 0xE00000 which are held by the acpi0 device. I don't know what it wants these ranges for, but if it can't map and access them, the MiniportInitialize() method fails. |
||
|---|---|---|
| .. | ||
| cfg_var.h | ||
| hal_var.h | ||
| kern_ndis.c | ||
| kern_windrv.c | ||
| ndis_var.h | ||
| ntoskrnl_var.h | ||
| pe_var.h | ||
| resource_var.h | ||
| subr_hal.c | ||
| subr_ndis.c | ||
| subr_ntoskrnl.c | ||
| subr_pe.c | ||
| subr_usbd.c | ||
| usbd_var.h | ||
| winx32_wrap.S | ||
| winx64_wrap.S | ||