fyi: WDM to KMDF Porting Guide

Discussion in 'Windows Vista Drivers' started by Eliyas Yakub [MSFT], Sep 13, 2006.

  1. Eliyas Yakub [MSFT], Sep 13, 2006
    1. Advertisements

  2. The porting guide says that it's possible to port NDIS miniports and
    protocol drivers.

    Is it possible to use KMDF for NDIS intermediate drivers (which are a sort
    of combination of a miniport and protocol)??

    Gianluca Varenni, Sep 13, 2006
    1. Advertisements

  3. No. You use KMDF to replace only the WDM edge of your driver. In an IM
    driver, there is no WDM edge. Both top and bottom edge is NDIS.

    Eliyas Yakub [MSFT], Sep 13, 2006
  4. But the usual "third" edge (i.e. the one interfacing with the app/other
    modules) can be KMDF instead of WDM with no problems (but probably there are
    no samples, considering the current passthru one doesn't have the "third

    Gianluca Varenni, Sep 13, 2006
  5. By third edge you mean the private ioctl interface thru control-device. No
    you can't do that with KMDF. Private ioctl interface can be provided only by
    the edge that owns your driver dispatch table. In the IM case, NDIS owns it.
    Exactly for this reason, when you write NDIS-WDF driver, you have to use
    NdisRegisterDevice to create control-device.
    Eliyas Yakub [MSFT], Sep 14, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.