HID KMDF Filter Driver

NTDEV
1

Dear Team,

I am working on src-kmdf-hidusbfx2. The sample consists of two folders hidmapper and sys. In the ReadMe file, it was clearly mentioned that mapper hidkmdf.sys can be used as is without any modifications.

In the Sys folder, hidusbfx2.inf file, we will add this KMDF of mapper just as a service.

On succesfully installing the device, the device manager shows only Mini Driver hidusbfx2.sys of sys but not hidkmdf.sys of mapper anywhere in the device list.

  1. What does it mean exactly by adding hidkmdf.sys as a service in the INF file. I am around this query because, inorder to obtain Windows Logo Program do I need to perform tests on hidkmdf.sys also.

  2. In DTM we need to mention the path of the inf file on the destination machine. Since I preinstalled drivers, the inf file is located both in the driver store and in the inf folder.
    Can somebody provice a pointer about the difference in selecting the inf file from the above said destinations.

The Common Scenario IO Tests fails when I select the inf from inf folder and gets passed when I select the inf file from the driver store.

Regards,
Uday Bhaskar.

2

>> 1. What does it mean exactly by adding hidkmdf.sys as a service in the

> INF file. I am around this query because, inorder to obtain Windows
> Logo Program do I need to perform tests on hidkmdf.sys also.

hidkmdf.sys (a WDM driver) would be considered a HID minidriver because it
registers with HIDClass driver by calling HidRegisterMinidriver(…) however
it forwards all the requests sent by HIDClass driver down to the KMDF driver
for processing, so all of the real work is done in KMDF driver. The sample’s
readme file has details on why this kind of driver layering was needed.

  • kumar

wrote in message news:xxxxx@ntdev…
> Dear Team,
>
> I am working on src-kmdf-hidusbfx2. The sample consists of two folders
> hidmapper and sys. In the ReadMe file, it was clearly mentioned that
> mapper hidkmdf.sys can be used as is without any modifications.
>
> In the Sys folder, hidusbfx2.inf file, we will add this KMDF of mapper
> just as a service.
>
> On succesfully installing the device, the device manager shows only Mini
> Driver hidusbfx2.sys of sys but not hidkmdf.sys of mapper anywhere in the
> device list.
>
> 1. What does it mean exactly by adding hidkmdf.sys as a service in the INF
> file. I am around this query because, inorder to obtain Windows Logo
> Program do I need to perform tests on hidkmdf.sys also.
>
> 2. In DTM we need to mention the path of the inf file on the destination
> machine. Since I preinstalled drivers, the inf file is located both in
> the driver store and in the inf folder.
> Can somebody provice a pointer about the difference in selecting the inf
> file from the above said destinations.
>
> The Common Scenario IO Tests fails when I select the inf from inf folder
> and gets passed when I select the inf file from the driver store.
>
> Regards,
> Uday Bhaskar.
>

3

Thanks for the response. I have gone through the ReadMe file of the sample before posting the query. The layering is because of the conflict of Dispatch Table ownership between KMDF definition and HID class driver.

But I got confused when only hidusbfx2.sys was shown in availabile driver list while testing the driver under DTM. When the viewing was changed from Submission View to Driver View both the drivers are getting displayed.

Regards.