Xiaofan Chen wrote: >> My vote is to unload. If not, the user should not use libftdi in the >> first place.
Agreed, though see the post in libusb-devel just now. Checking active and then unloading may be racy, if I understand the original thread from a year and half ago right. Between when you decided to unload and when you actually unload ftdi_sio, another program may have already unloaded ftdi_sio itself. We need a way to check after detaching just what we detached, and, even then, it's not good. >> > -- some other application has claimed the device via usbfs, should we force >> > claiming and continue or should we exit >> >> Either way. I would more inclined to exit and I tend to think it is a current >> libusb bug so that you can force claiming. I would certainly not blindly detach usbfs. Either give the option via an argument or exit. >> > -- If we unloaded ftdi_sio, should we attach it again on exit >> >> Either way. Not sure. Michael -- libftdi - see http://www.intra2net.com/en/developer/libftdi for details. To unsubscribe send a mail to [email protected]
