From: Robert H. <he...@de...> - 2005-03-14 11:54:55
|
gerard klaver <ge...@gk...>, In a message on Mon, 14 Mar 2005 12:28:51 +0100, wrote : gk> On Mon, 2005-03-14 at 13:24 +0200, Alexandru Cristescu wrote: gk> > Hi, gk> > gk> > I'm trying to do usb_claim_interface() (or usb_control_msg() for that gk> > matter) and I get -EBUSY error code. I browsed through this mailing list gk> > and I understand the problem comes from the fact that the kernel claims gk> > the device (in fact there is a hiddev0 in /dev ) but I could not find a gk> > definite answer. gk> > gk> > My question is: is there a workaround? (that doesn't involve recompiling gk> > the kernel). I'm running FC3 (kernel 2.6.9) gk> > gk> > Thanks in advance.. gk> > gk> > gk> > gk> With rmmod <kernel moduled> try to remove the kernel module which is gk> blocking your device from access true libusb. gk> gk> Or place the kernel module name in the /etc/hotplug/blacklist file Or use the usb_detach_kernel_driver_np() function. gk> -- gk> -------- gk> m.vr.gr. gk> Gerard Klaver gk> gk> gk> gk> ------------------------------------------------------- gk> SF email is sponsored by - The IT Product Guide gk> Read honest & candid reviews on hundreds of IT Products from real users. gk> Discover which products truly live up to the hype. Start reading now. gk> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click gk> _______________________________________________ gk> Libusb-devel mailing list gk> Lib...@li... gk> https://lists.sourceforge.net/lists/listinfo/libusb-devel gk> gk> \/ Robert Heller ||InterNet: he...@cs... http://vis-www.cs.umass.edu/~heller || he...@de... http://www.deepsoft.com /\FidoNet: 1:321/153 |