Menu
▾
▴
Re: [Libusb-devel] libusb on OSX keeps returning -EBUSYfor claim_interface
|
From: Dan E. <dan...@ne...> - 2008-01-19 01:12:30
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Jorgen Lundman wrote: <blockquote cite="mid:46D...@lu..." type="cite"> <meta http-equiv="Content-Type" content="text/html; "> <meta name="Generator" content="MS Exchange Server version 6.5.7652.24"> <title>Re: [Libusb-devel] libusb on OSX keeps returning -EBUSYfor claim_interface</title> <!-- Converted from text/plain format --> <p><font size="2"><br> It is pretty easy, but it requires a reboot to force it to unload the OS<br> HID reference. Personally I do not consider that acceptable, so libusb<br> and libhid are unfortunately next to useless on OsX if your device is<br> picked up by OsX's HID. Otherwise they work great.<br> <br> Eventually someone will work out the OsX HID magic needed to talk to a<br> HID device and that could be rolled into libusb/libhid.<br> </font></p> </blockquote> <font size="2">Similar work has occured on libusb-win32 - it can connect to the HID driver interface instead of the generic interface. It doesn't seem unreasonable that libusb should attempt to connect to interfaces which haven't been handled by the OS (or other applications).<br> <br> A reboot is obviously not the correct solution!<br> <br> Dan.<br> </font> </body> </html> |