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 hid
module is inserted (e.g. a USB keyboard is attached to the system) I
can no longer use the libusb interface because it says the endpoint is
busy. So I've been playing around with the /dev/usb/hiddevX
interface, but haven't been able to make too much sense of the output.
my read() will get data (not the right amount, and not every time)
when I send it from the device, but it's not in any format I can
discern.
Is using the hiddev interface even the correct approach for doing
this? Does anyone have any suggestions on how I can get this to work?
FYI, I'm developing on a SuSE 9.0 box with a 2.4.21 kernel. I don't
have the luxury of using a 2.6 kernel, as the customer requires SuSE
9.0
Thanks.
-Jeff
I developed a user application that used the hiddev (Suse 9.0). Just
opened /dev/usb/hiddev0. Then I just sent and received HID reports.
The only problem that I noticed with Suse 9.0 (or Linux 2.4 kernel), is
it throws away what it considers duplicate reports. My device was a USB
credit card reader. If someone swiped a card twice, the second swipe
was being tossed by the kernel. I have a patch to try to see if it
clears it up.
Ken Cobler
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
