multiple Monitors and Video Present Networks
This article writes something VidPN. Microsoft's explanation/Description of sample code is getting "stingy". At least, before taking a sample from the WDK/DDK out, take a look, change a change, try, but also play a game, from the actual driver run to understand the driving situation. With a more perceptual understanding, then go into the detailed code, or have the goal to change the code, it seems to be more lost, less.
In order to evaluate the workload of the display drive, to understand how the display driver works, and to achieve the feasibility of the display drive, from the manpower, time to make an estimate, to find the mirror driver in the WDK, perhaps due to my limited ability, coupled with the lack of knowledge of graphics drivers, Leng didn't play anything out of Mirror's sample.
Helpless, and went to find a WIN8 based on the sample. http://msdn.microsoft.com/en-us/library/ff554076 (v=vs.85). aspx
Kernel Mode display-only Miniport Driver (kmdod) sampleCompared to mirror, this drive is closer to my project, as well as the content of the evaluation.
As for the contents of this sample, we'll take the time to write it, and here we'll write something about the content of the VidPN. The VidPN Manager works with display DRIVER and miniport DRIVER to jointly manage adapter and devices connected on adapter.
Simply put, VidPN is the logical representation of the graphics driver, which is the path of the source, the target, the connection source and the target (a specific path that represents the specific conversion function, such as contrast/brightness gains, flicker filter, color Transformation), the source pattern and pattern collection, the target pattern and pattern set, the topology structure of the path, the collection of source patterns of the display, and so on.
The main responsibilities of VidPN manager include the following:
For the plug of the monitor, the unplug responds to the management of the mode collection of the adapter connected display and updates the management of the source-to-target correlation to adjust and manage the display device and display mode (in the case of open, close, dock, undock, respectively)
The following paragraphs seem to convey more clearly the meaning of VidPN.
The hardware on a display adapter that's responsible for scanning rendered content from video memory and presenting it on Video outputs is called the display adapter ' s presentational subsystem. A video present network (VidPN) is a software model of a display adapter ' s presentational subsystem.
The key elements of a display adapter ' s presentational subsystem is the views (primary surface chains) and the video OUTP UTs. In the VidPN model, a view was called video present source, and a video output is called a video present target.
A video present path is an association between a video present source and a video present target. A VidPN models the relationship between sources and targets by maintaining a set of video present paths. The set of paths is called AVIDPN topology.
Note that video present targets is not the monitors (or other external display devices) connected to the display adapter. The video present targets is the video output connectors themselves.
One point to emphasize: the pattern of source and target is changed with the change of topology, not a static concept. The role of miniport is to correlate specific codec, and this associated work is transparent to the upper user mode. A codec can connect to a source, but can connect multiple target, which is the way to do it:
