<br>Yes I can follow the code in hid_interrupt_write(). But what does that mean?<br>Does that mean libhid and libusb cannot be used to talk to my device?<br>It looks like I cannot set/get report (for write() and read()). But what does that mean?
<br>Am I missing a step in the setup so report descriptors were not made available?<br><br><div><span class="gmail_quote">On 9/28/06, <b class="gmail_sendername">Charles Lepple</b> <<a href="mailto:clepple@ghz.cc">clepple@ghz.cc
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Sep 28, 2006, at 8:09 PM, Mark S. Townsley wrote:<br><br>> More info....
<br>><br>><br>> Before I go into all the libhid stuff, I actually called libusb<br>> stuff, specifically<br>> to usb_detach_kernel_driver_np().<br><br>If you are calling libusb functions directly, you should be able to
<br>follow the code in hid_interrupt_write.<br><br>> Since seeing the "could not detach from kernel errors", I comment<br>> out the code,<br>> rmmod the hid driver, and now interrupt_write()/read() returns this
<br>> error:<br>><br>> No error hid_interrupt_write 1 failed with return code 21<br>><br>><br>> I have hid_set_debug(10);<br>><br>> What does return code 21 means?<br><br>Return codes are enumerated here:
<br><br><a href="http://www.ghz.cc/~clepple/libhid/doc/html/hid_8h.html#a64">http://www.ghz.cc/~clepple/libhid/doc/html/hid_8h.html#a64</a><br><br>Check the source for hid_interrupt_write:<br><br><a href="http://www.ghz.cc/~clepple/libhid/doc/html/hid__exchange_8c-">
http://www.ghz.cc/~clepple/libhid/doc/html/hid__exchange_8c-</a><br>source.html#l00380<br><br>--<br>Charles Lepple<br><a href="mailto:clepple@ghz.cc">clepple@ghz.cc</a><br><br><br></blockquote></div><br>