![]() ![]() 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 should not 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) does not call the DxgkDdiQueryInterface function to query the Miracast display interface, then it does not support Miracast wireless displays, and the display miniport driver should not report any Miracast target. If the 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, Windows Display Driver Model (WDDM) display miniport drivers that run in kernel mode need to do the following tasks. Support for custom Miracast implementations may be removed in a future version of Windows. Drivers should no longer implement a custom Miracast display component. ![]() As of Windows 10, the OS contains a native implementation of Miracast wireless displays. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |