Export (0) Print
Expand All

Which Drivers Can Be Ported and Where

This topic describes which WDM drivers can be ported to Windows Driver Frameworks (WDF), and how to decide whether to port to Kernel-Mode Driver Framework (KMDF) or User-Mode Driver Framework (UMDF).

Which WDM drivers can I port to WDF?

Whether a particular driver can be ported to WDF depends on the following criteria:

  • The operating system versions on which the driver runs
  • The type of device that the driver supports
  • The driver model that the driver uses

In general, you can use KMDF or UMDF to write drivers that conform to WDM, supply entry points for the major I/O dispatch routines, and handle IRPs.

For some device types, system-supplied device class and port drivers provide driver dispatch functions and call a vendor-supplied miniport driver to handle specific I/O details. These miniport drivers are essentially callback libraries and are not supported by WDF. In addition, WDF does not support device types that use Windows Image Acquisition (WIA).

You can use KMDF to create drivers that run on Windows 2000 and later. You can use UMDF version 1 to write drivers that run on Windows XP and later, and UMDF version 2 to target Windows 8.1 and later.

For information about device and driver types that UMDF and KMDF support, see Choosing a Driver Model.

Which framework should I port my WDM driver to, KMDF or UMDF 2?

  1. Review the list of KMDF-only functionality in Comparing UMDF 2.0 Functionality to KMDF. If your driver does not require any of these features, and you are targeting Windows 8.1 or later, open a new UMDF 2 driver template in Visual Studio.

    If you realize later that you need a KMDF-only feature, it's straightforward to convert your UMDF 2 driver to KMDF, as described in How to convert a KMDF driver to a UMDF 2.0 driver (and vice-versa).

  2. You can also write a mode-agnostic driver, meaning one that can be compiled using either KMDF or UMDF. To write a mode-agnostic driver, start with a UMDF 2 template. Use the DDI versioning info listed in Summary of WDF Callbacks and Methods to ensure that you only call methods that are available in both KMDF and UMDF 2. Conditionally tag any header references with the preprocessor macros described in How to convert a KMDF driver to a UMDF 2.0 driver (and vice-versa). To switch your driver, you would create an empty driver project using a Visual Studio template for the target framework, and copy your source code over.

Related topics

Getting Started with UMDF
KMDF Version History
UMDF Version History
User-Mode Driver Framework Frequently Asked Questions

 

 

Send comments about this topic to Microsoft

Show:
© 2014 Microsoft