KMDF was designed to replace the Windows Driver Model (WDM). As I've pointed out in previous articles, if your device doesn't handle interrupts, perform direct memory access (DMA), or require other kernel mode resources such as non-paged pool memory, you should consider writing a user mode driver (UMDF) instead. This article provides an introduction to the architecture and features of KMDF and to the requirements for drivers that use KMDF (sometimes called KMDF-based drivers or simply KMDF drivers). Objects are organized hierarchically in a parent/child model, and important driver data structures are maintained by KMDF rather than by the driver. KMDF provides a well-defined object model and controls the lifetime of objects and memory allocations. KMDF implements code to handle common driver requirements drivers customize the framework by setting object properties, registering callbacks to be notified of important events, and including code only for features that are unique to their device. In essence, the framework is a skeletal device driver that can be customized for specific devices. It provides a C-language device-driver interface (DDI) and can be used to create drivers for Windows 7. KMDF is an infrastructure for developing kernel mode drivers. The Kernel Mode Driver Framework (KMDF) is the second of two major sub-frameworks in the Windows Driver Foundation (WDF) Framework.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |