如何获取 PCI 设备的配置和位置信息(国外英语资料).docVIP

如何获取 PCI 设备的配置和位置信息(国外英语资料) On Windows NT 4.0, the driver scans the bus and calls HalGetBusData and HalGetBusDataByOffset to get this information. In Windows 2000 and higher versions of the Windows operating system, the hardware bus is controlled by their respective bus drivers, not HAL. As a result, all the Hal apis used to provide bus related information are out of date in the Windows 2000 and later versions of the Windows operating system. In Windows 2000 and the higher version of the Windows operating system, the driver does not need to query the device to find the resource. The driver requests this resource through the IRP_MN_START_DEVICE request of the plug and play (PnP) manager. Usually, the driver that is written correctly doesnt need any of this information to work properly. If for some reason the driver needs to get this information, refer to the code example below for the resource. The driver should be part of the device driver stack because it requires the devices basic physical device object (PDO) to send the PnP request. The following code example demonstrates how to get the configuration information: NTSTATUS ReadWriteConfigSpace ( IN PDEVICE_OBJECT DeviceObject points, IN ULONG ReadOrWrite, / / 0 for read 1 for write IN PVOID Buffer, IN ULONG Offset, IN ULONG Length ) { KEVENT event; NTSTATUS status; PIRP irp. IO_STATUS_BLOCK ioStatusBlock; PIO_STACK_LOCATION irpStack; PDEVICE_OBJECT targetObject points; PAGED_CODE (); KeInitializeEvent ( NotificationEvent ); TargetObject = iogetattacheddevicerence (DeviceObject); Irp = iobuildsynchronousousfsdrequest (IRP_MJ_PNP) TargetObject, NULL, 0, NULL, event, ioStatusBlock); If (irp = = NULL) { Status = STATUS_INSUFFICIENT_RESOURCES; Goto the End; } IrpStack = IoGetNextIrpStackLocation (irp); If (ReadOrWrite = = 0) { IrpStack - MinorFunction = IRP_MN_READ_CONFIG; } else { IrpStack - MinorFunction = IRP_MN_WRITE_CONFIG; } The irpStack - parameter.readwriteconfig. The irpStack - parameter.readwriteconfig.