> I'm puzzled. So far as I can tell, the only reason for getting -EBUSY > from a claim_interface call is because there is another driver bound to > the interface. Yes, and the call to usb_detach_kernel_driver_np actually solved it, but I was calling it on the the wrong interface (:-( It works now.
> Does your program open the device file before or after the firmware > download is complete? Perhaps you need to open (or re-open) it after > the firmware is all sent. I've done some tests and it doen't seem to change things. Thanks Alan. -- Guillaume Dargaud http://www.gdargaud.net/Climbing/ ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
