From: heejune on
Thanks all for the replies before and I'd like to ask few more
questions related to VidPN management of WDDM driver.

When WDDM miniport driver enumeratse child devices and connected
external monitors, it first detects its all child devices in
DxgkDdiQueryChildRelations, and next check each child actually has
connected output in DxgkDdiQueryChildStatus. So, to implement adding
another(virtual) monitor I faked one of given PDXGK_CHILD_STATUS
parameter(HotPlug.Connected) to have true. And I filled up followed
EDID query requests as well.

Then I could see another monitor attached on desk.cpl, but unable to
manipulate it. Extending into second(faked) monitor keeps failing. It
seems miniport was not able to find targetid associated with given
sourceid & path in DxgkDdiCommitVidPn..

If there's anything that I'm missing here, really appreciate any idea
or comment. Thanks.
From: heejune on
one more symtom: DxgkDdiQueryChildStatus is not called for faked child
only during enumerate it after clicked 'Apply".

On 3¿ù2ÀÏ, ¿ÀÀü11½Ã18ºÐ, heejune <heej...(a)gmail.com> wrote:
> Thanks all for the replies before and I'd like to ask few more
> questions related to VidPN management of WDDM driver.
>
> When WDDM miniport driver enumeratse child devices and connected
> external monitors, it first detects its all child devices in
> DxgkDdiQueryChildRelations, and next check each child actually has
> connected output in DxgkDdiQueryChildStatus. So, to implement adding
> another(virtual) monitor I faked one of given PDXGK_CHILD_STATUS
> parameter(HotPlug.Connected) to have true. And I filled up followed
> EDID query requests as well.
>
> Then I could see another monitor attached on desk.cpl, but unable to
> manipulate it. Extending into second(faked) monitor keeps failing. It
> seems miniport was not able to find targetid associated with given
> sourceid & path in DxgkDdiCommitVidPn..
>
> If there's anything that I'm missing here, really appreciate any idea
> or comment. Thanks.