Hi,
I created a UMDF 2 based HID mini driver, which is working as expected. I am able to receive input reports , send output reports , set/get features.
My driver is not receiving any custom IOCTLS, as HidClass driver is managing those IOCTL management and never propagate to the layer i am in . If my driver was a KMDF one , i could use Raw PDO approach for side band communications . Is there a similar way i can achieve the same in UMDF 2 ? ( control code based side band communications mentioned in vhidmini example doesn’t work for me for many reasons,so i am looking for a different solution). Unfortunately moving to KMDF is not an option for me
Thanks for any help in advance
Report a new TLC and route the commands via hid reports, never sending them to the hardware, rather always completed at the miniport layer
d
Bent from my phone
From: xxxxx@gmail.commailto:xxxxx
Sent: ?11/?24/?2013 8:07 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] UMDF 2 HID mini side band communication help
Hi,
I created a UMDF 2 based HID mini driver, which is working as expected. I am able to receive input reports , send output reports , set/get features.
My driver is not receiving any custom IOCTLS, as HidClass driver is managing those IOCTL management and never propagate to the layer i am in . If my driver was a KMDF one , i could use Raw PDO approach for side band communications . Is there a similar way i can achieve the same in UMDF 2 ? ( control code based side band communications mentioned in vhidmini example doesn’t work for me for many reasons,so i am looking for a different solution). Unfortunately moving to KMDF is not an option for me
Thanks for any help in advance
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>
Hi Doron, Thanks for the response. My hid mini exposes some of the functionality where users can use using hid user mode API(hid.dll) and Windows.Devices.HumanInterfaceDevice API , and the one i try to achieve using custom IOCTL is some configuration related feature , intended only for some specific users , but not all. if i introduce a new TLC , still that is available for users via hid user mode API ? if so that is what i want to avoid (please correct me if my understanding is wrong)
Yes, the new TLC would be available to all users. You can put it into a a custom usage/page if that helps mitigate the issue. If you need a modern app to talk to your private channel, you would need the raw PDO only available in KMDF. If you are configuring from a desktop app, you can use a raw pdo or control device