HID question...

Hi.
I have a driver (based on Walter Oney’s PDOFILT) that is sitting between
HIDUSB and MOUHID/KBDHID as a filter driver. I’m hunting around for the
format of the data returned from the HID class driver when MOUHID or
KBDHID do an IRP_MJ_READ…
I’ve been digging through the HID documents for the report types, but was
wondering if anyone knew if the information HIDCLASS/HIDUSB returns is in
a standard HID input report format (depending on which device the IRP is
from - mouse or keyboard) or if, since only the report buffer is filled in
by HIDCLASS/HIDUSB, the data is in a non-standard/undocumented format?

Thanks,
sean

Mouhid / kbdhid are normal HID clients. They use the same buffer you
would send from user mode and follow the same methodology (get the hid
preparsed data, get the input report length off of the HIDP_CAPS and
then sends reads down of that length. Kbdhid / mouhid speak pure HID,
they don’t know where the HID data comes from (usb, Bluetooth, over the
Ethernet, etc etc).

D

This posting is provided “AS IS” with no warranties, and confers no
rights

-----Original Message-----
From: xxxxx@stg.com [mailto:xxxxx@stg.com]
Sent: Thursday, March 06, 2003 8:58 AM
To: NT Developers Interest List
Subject: [ntdev] HID question…

Hi.
I have a driver (based on Walter Oney’s PDOFILT) that is sitting between
HIDUSB and MOUHID/KBDHID as a filter driver. I’m hunting around for the
format of the data returned from the HID class driver when MOUHID or
KBDHID do an IRP_MJ_READ…
I’ve been digging through the HID documents for the report types, but
was
wondering if anyone knew if the information HIDCLASS/HIDUSB returns is
in
a standard HID input report format (depending on which device the IRP is
from - mouse or keyboard) or if, since only the report buffer is filled
in
by HIDCLASS/HIDUSB, the data is in a non-standard/undocumented format?

Thanks,
sean


You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Cool… that’s what I thought. Thanks for the response!

sean