[libhid-discuss] Cannot claim interface 0

[Mark S. Townsley]

I have a line in my code:  hid_set_usb_debug(0).
However, I have noticed something.

If I have

   mount -t usbfs none /dev/bus/usb

then my hid_interrupt_write()/read() get the error:   "could not claim
interface 0: device or resource busy".


If I don't have /dev/bus/usb mounted,
I get a different error:   "could not detach kernel driver from interface 0:
No data available.


Is there some "setup" I need to do so interface 0 is available for me to do
interrupt_write()/read()?

Mark


On 9/28/06, Charles Lepple <clepple at ghz.cc> wrote:
>
> Mark S. Townsley wrote:
> > Hi:
> >
> > I am using hid_interrupt_write() and hid_interrupt_read() to talk to my
> > HID
> > device.  But both calls come back with an error saying:
> >
> >   "could not claim interface 0: Device or resource busy".
>
> What is the full error message? Is this from setting USB_DEBUG to
> something non-zero?
>
> > But my hid_force_open() issues earlier in the same code (and remains
> open)
> > was successful.
> > Shouldn't hid_force_open() already claim the required interface so
> > interrupt_write/read can use
> > the claimed interface?
>
> Yes, it should be taken care of in hid_force_open().
>
> --
> Charles Lepple
> clepple at ghz.cc
>
>
> _______________________________________________
> libhid-discuss mailing list
> libhid-discuss at lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/libhid-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/libhid-discuss/attachments/20060928/5f37e023/attachment.htm