microsoft / microsoft/wdkmetadata

Support IddCx.h

Open
#49 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
110
Forks
15
PR merge metrics
No merged PRs in 30d

Description

A bit of background for my request, (specifically, I'm using iddcx 1.9)

So, I went ahead and followed the official idd sample driver and manually created bindings to the entire WDK and Idd for my driver project. And I got a working umdf driver now,

To that end, the specific functions I used since I couldn't find them in the generated bindings (and please correct me if I am wrong anywhere), are:

Idd:
IddCxDeviceInitConfig, IddCxDeviceInitialize, IddCxAdapterInitAsync, IddCxMonitorCreate, IddCxMonitorArrival, IddCxSwapChainSetDevice, IddCxSwapChainReleaseAndAcquireBuffer, IddCxSwapChainFinishedProcessingFrame

Wdf:
WdfDriverCreate, WdfDeviceCreate, WdfDeviceInitSetPnpPowerEventCallbacks, WdfObjectGetTypedContextWorker (this is internal, but I needed to recreate the WDF_DECLARE_CONTEXT_TYPE!() macro), WdfObjectDelete

Also had to manually export FxDriverEntryUm entry point to get the ball rolling.

Thanks for all your guys effort! I would absolutely love to throw away all my bindings 😄

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the generated bindings with IddCx.h and the listed IddCx and WDF functions, then inspect the wdkmetadata generation path. Use the linked virtual-display-rs files as a reference for the missing declarations. Done means the generated output exposes the requested APIs, including the needed driver entry point and context support.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, rust
Domain
devtools, operating-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.