I’m working on one project about getting raw HID report desciptor of one of our USB products and then parse it.
Now I can’t figure out how to do that.
Can anyone have such a exprience on how to get the raw data? Do I need to write any kernel mode filter drivers?
The HID stack itself does not provide a way to extract a raw HID descriptor. You could force WinUSB to load on the HID device (instead of hidusb), and then get the HID descriptor yourself.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Tuesday, January 06, 2009 10:08 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to get the HID report descriptor
I’m working on one project about getting raw HID report desciptor of one of our USB products and then parse it.
Now I can’t figure out how to do that.
Can anyone have such a exprience on how to get the raw data? Do I need to write any kernel mode filter drivers?
NTDEV is sponsored by OSR
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
Well, if it’s a genuine USB HID device then any USB sniffer will publish the HID report descriptor with no development needed, that’s easy enough.
What about non-USB HID devices though, Randy? Apart from good ol’ hooking, is there a legitimate enough way to observe the IOCTL_HID_GET_REPORT_DESCRIPTOR output? One can’t really insert a filter driver between the HIDCLASS and its miniport as the pair is a single WDM driver for the PnP purposes.
-----Original Message-----
From: Randy Aull xxxxx@windows.microsoft.com
Sent: Wednesday, January 07, 2009 10:16 AM
To: Windows System Software Devs Interest List
RE: How to get the HID report descriptor
The HID stack itself does not provide a way to extract a raw HID descriptor.
You could force WinUSB to load on the HID device (instead of hidusb), and then
get the HID descriptor yourself.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Tuesday, January 06, 2009 10:08 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to get the HID report descriptor
I’m working on one project about getting raw HID report desciptor of one of our
USB products and then parse it.
Now I can’t figure out how to do that.
Can anyone have such a exprience on how to get the raw data? Do I need to write
any kernel mode filter drivers?
If it achieves your goal, then using a USB sniffer is probably the easiest way to see the descriptor.
Unfortunately there isn’t really a good solution for generically extracting the raw report descriptors.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Wednesday, January 07, 2009 6:49 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] How to get the HID report descriptor
Well, if it’s a genuine USB HID device then any USB sniffer will publish the HID report descriptor with no development needed, that’s easy enough.
What about non-USB HID devices though, Randy? Apart from good ol’ hooking, is there a legitimate enough way to observe the IOCTL_HID_GET_REPORT_DESCRIPTOR output? One can’t really insert a filter driver between the HIDCLASS and its miniport as the pair is a single WDM driver for the PnP purposes.
-----Original Message-----
From: Randy Aull xxxxx@windows.microsoft.com
Sent: Wednesday, January 07, 2009 10:16 AM
To: Windows System Software Devs Interest List
RE: How to get the HID report descriptor
The HID stack itself does not provide a way to extract a raw HID descriptor.
You could force WinUSB to load on the HID device (instead of hidusb), and then
get the HID descriptor yourself.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@hotmail.com
Sent: Tuesday, January 06, 2009 10:08 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How to get the HID report descriptor
I’m working on one project about getting raw HID report desciptor of one of our
USB products and then parse it.
Now I can’t figure out how to do that.
Can anyone have such a exprience on how to get the raw data? Do I need to write
any kernel mode filter drivers?
NTDEV is sponsored by OSR
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