VideoPortGetDeviceBase - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// video.h
VIDEOPORT_DEPRECATED VIDEOPORT_API PVOID VideoPortGetDeviceBase(
PVOID HwDeviceExtension,
PHYSICAL_ADDRESS IoAddress,
ULONG NumberOfUchars,
UCHAR InIoSpace
);
View the official Windows Driver Kit DDI referenceNo description available.
The VideoPortGetDeviceBase function maps a range of bus-relative device memory or I/O addresses into system space.
HwDeviceExtensionPointer to the miniport driver's device extension.
IoAddressThe base physical address of the range to map. You get this bus-relative value by calling VideoPortGetDeviceData, VideoPortGetRegistryParameters, or VideoPortGetAccessRanges. Otherwise, this value is a driver-supplied, default base address for the device memory or I/O ports.
You must have successfully claimed the range described by IoAddress and NumberOfUchars in the registry through a preceding call to VideoPortVerifyAccessRanges or VideoPortGetAccessRanges.
NumberOfUcharsThe number of bytes, starting at IoAddress, to map.
InIoSpaceThe location of the IoAddress range. This parameter can be one of the following flags or an ORed, compatible combination of these flags.
| Flag | Meaning |
|---|---|
| VIDEO_MEMORY_SPACE_DENSE | Obsolete. |
| VIDEO_MEMORY_SPACE_IO | The address range is in I/O space, not in memory space. |
| VIDEO_MEMORY_SPACE_MEMORY | The address range is in memory space, not in I/O space. |
| VIDEO_MEMORY_SPACE_P6CACHE | The processor aggregates a sequence of write operations, sends them to a cache line, and later flushes the cache. This flag is meaningful only when VIDEO_MEMORY_SPACE_IO is not set. Designates the video memory as write-combined (WC). For information about WC caching, see the Write-Combining Memory in Video Miniport Drivers website article. |
If successful, VideoPortGetDeviceBase returns the base virtual address of the mapping. If the specified bus-relative range cannot be mapped, VideoPortGetDeviceBase returns NULL.
You can pass the mapped virtual addresses to the VideoPortReadXxx, VideoPortWriteXxx, and VideoPortXxxMemory functions, except for VideoPortMapMemory and VideoPortUnmapMemory.
You must call VideoPortGetDeviceBase from the miniport driver's HwVidFindAdapter, HwVidQueryDeviceCallback, or HwVidQueryNamedValueCallback function.
Before HwVidFindAdapter returns control, you should store both the mapped base address returned by VideoPortGetDeviceBase and the length of the mapped access range in the adapter's device extension (pointed to by HwDeviceExtension) for later use.
Access to the mapped address space must follow these rules:
VideoPortGetDeviceBase and VideoPortMapMemory can both be called by the video miniport driver to map video memory into a virtual address space. If you call both of these functions to map the same physical addresses, or if you call one of the functions more than once to map the same physical addresses, you might have more than one virtual-address range that maps to the same physical-address range. In that case, you must set the VIDEO_MEMORY_SPACE_P6CACHE flag of the InIoSpace parameter to the same value in all of those calls.
Every universal memory architecture (UMA) display device uses a frame buffer that is located in main memory rather than on a PCI bus. In this case, do not call VideoPortMapMemory to map the frame buffer. To map a UMA frame buffer into system space, call MmMapIoSpace.
If a miniport driver does not support an adapter that it has mapped a logical range for, it must perform two steps before it returns control to the DriverEntry function: call VideoPortFreeDeviceBase to unmap the previously mapped range from system space, and call VideoPortGetAccessRanges or VideoPortVerifyAccessRanges to release its claims on the range in the registry.
VideoPortGetRegistryParameters