![]() The user-mode driver can access this private driver data in the MIRACAST_CHUNK_DATA. pPrivateDriverData and PrivateDataDriverSize members in the DXGKARGCB_NOTIFY_INTERRUPT_DATA structure. In response to this interrupt, the display miniport driver must call the DxgkCbNotifyInterrupt function and complete the MiracastEncodeChunkCompleted child structure in the DXGKARGCB_NOTIFY_INTERRUPT_DATA structure, including setting the DXGK_INTERRUPT_TYPE interrupt type to DXGK_INTERRUPT_MICACAST_CHUNK_PROCESSING_COMPLETE.Īs part of the interrupt handling, the driver can optionally specify the MiracastEncodeChunkCompleted. Each time the GPU finishes encoding one of these chunks, it must generate an interrupt. The data for a single frame transmitted across the wireless Miracast connection can be broken into one or more encode chunks. Handling interrupts for completed encode chunks For example, if the Miracast sink vertical refresh rate is 240 Hz and the VSync interrupt frequency of the connected display is 30 Hz, the driver should set VsyncFreqDivider to 8. VsyncFreqDivider, which is the ratio of the VSync rate of a monitor that displays through a Miracast connected session to the VSync rate of the Miracast sink. The driver must specify the value of D3DKMDT_VIDEO_SIGNAL_INFO. If a monitor is connected to the Miracast sink, the driver should set Miracast. Type to a value of StatusMiracast and should use the Miracast child structure in DXGK_CHILD_STATUS. The display miniport driver should set DXGK_CHILD_STATUS. When the Miracast session has been started, the operating system calls the DxgkDdiQuer圜hildStatus function. Queries the Miracast capabilities of the current display adapter. Processes a synchronous I/O request that originates from a Miracast user-mode driver call to MiracastIoControl. The following table lists the Miracast functions that the WDDM 1.3 display miniport driver implements: FunctionĬreates a context to start a kernel-mode instance of a Miracast display device. ![]() If the Miracast sink is embedded in the monitor or TV, this member should be set to the D3DKMDT_VOT_MIRACAST constant value of the D3DKMDT_VIDEO_OUTPUT_TECHNOLOGY enumeration. Value that indicates the connection type. StatusMiracast constant value of the DXGK_CHILD_STATUS_TYPE enumeration In this call, the driver should set the following values in the DXGK_CHILD_STATUS structure: Member When a Miracast session is starting, and a monitor is connected to the Miracast sink or the driver receives an I/O request from the Miracast user-mode driver because a new monitor has connected to the Miracast sink, the display miniport driver should report a monitor arrival hot-plug detection (HPD) awareness value to the operating system by calling the DxgkCbIndicateChildStatus function. ![]() The Miracast target should remain in a disconnected state until Dxgkrnl starts a Miracast connected session. The driver shouldn't report more than one Miracast target on any full WDDM graphics device, otherwise the operating system fails to start the adapter.Īfter Dxgkrnl calls DxgkDdiQueryInterface to query the Miracast display interface, the driver can then report the target type as D3DKMDT_VOT_MIRACAST during device initialization when Dxgkrnl calls the DxgkDdiQuer圜hildRelations function. If the operating system's DirectX graphics kernel subsystem (Dxgkrnl.sys) doesn't call the DxgkDdiQueryInterface function to query the Miracast display interface, then it doesn't support Miracast wireless displays, and the display miniport driver shouldn't report any Miracast target. If the WDDM 8.1 display miniport driver supports Miracast displays, it must report the DXGK_MIRACAST_DISPLAY_INTERFACE structure, which has pointers to driver-implemented Miracast functions, when the Microsoft DirectX graphics kernel subsystem calls the DxgkDdiQueryInterface function. To support Miracast wireless displays on Windows 8.1, WDDM 1.3 display miniport drivers that run in kernel mode need to do the following tasks. Microsoft might remove support for custom Miracast stacks in a future version of Windows. The relevant WHLK documentation at .WirelessDisplayĭriver developers should no longer implement a custom Miracast stack. For information about the Microsoft Miracast stack and the requirements of drivers and hardware to support Miracast displays starting in Windows 10, see the following documentation:īuilding best-in-class Wireless projection solutions with Windows 10 Starting in Windows 10 (WDDM 2.0), the operating system ships with a built-in Miracast stack that can work on any GPU.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |