Jeff Lange wrote:
Johannes, the device is fully HID
compliant, it is just a vendor defined usage. The reason for this was
to make Windows driver a lot easier to write. I think I'm just going
to have to write my own kernel driver for this thing and create a char
dev that my app can read the dat
Ken,
I too am writing a USB MSR =). Johannes, the device is fully HID
compliant, it is just a vendor defined usage. The reason for this was
to make Windows driver a lot easier to write. I think I'm just going
to have to write my own kernel driver for this thing and create a char
dev that my a
Jeff Lange wrote:
Hi all,
I'm developing a simple USB device that reports itself as a HID
device, and uses interrupt transfers to send about 250 bytes of data
whenever an event occurs on the device. I've managed to communicate
with it and get the data using libusb, but I've found that if the
On Wed, 2005-06-08 at 12:37 -0400, Jeff Lange wrote:
> I'm developing a simple USB device that reports itself as a HID
> device, and uses interrupt transfers to send about 250 bytes of data
> whenever an event occurs on the device.
Why do you do this as opposed to *not* identifying as a HID dev
Hi all,
I'm developing a simple USB device that reports itself as a HID
device, and uses interrupt transfers to send about 250 bytes of data
whenever an event occurs on the device. I've managed to communicate
with it and get the data using libusb, but I've found that if the hid
module is insert
Hello,
If I'm understanding everything correct you should do this to get a
feature report to a usb device:
/* set report_type and report_id in rinfo */
IOCGREPORTINFO(struct hiddev_report_info* rinfo)
IOCGREPORT(struct hiddev_report_info* rinfo)
/* set uref's report_id, report_type field_index
