On Tue, Feb 12, 2013 at 6:29 PM, Hans de Goede <hdego...@redhat.com> wrote: > Note: > 1) I'm not claiming this is easy from an implementation pov, just that > the current API can handle this. > > 2) AFAIK Mac OS X is actually in more or less a similar situation, it has > a call to detach the in kernel driver, but the in kernel driver can > refuse, and most do. A solution to this is to install a stub driver instead > which does allow detaching, at which point the situation is more or less > the same as under Windows. > > So these event types may be useful for Mac OS X too, although I wonder if it > is possible to find out if detaching will work without trying? Maybe libusb's > Mac OS X code can contain a list of driver-names for drivers known to fail > detach and use that to signal the difference?
If you want to find a way to detach kernel driver under Mac OS X using a programmatically way, you will be disappointed to find that it is not possible! Ref: http://libusb.6.n5.nabble.com/No-way-to-programmatically-unload-a-driver-and-grab-the-IOUSBDevice-or-IOUSBInterface-from-user-space-td5710987.html http://lists.apple.com/archives/usb/2012/Dec/msg00003.html "There is no way to programmatically unload a driver to be able to grab the IOUSBDevice/IOUSBInterface from user space. We are well aware of the desire to do that so there is no need to file another bug report. The only solution is to create a codeless kext that will grab that IOUSBDevice/Interface and prevent any kernel drivers from loading for it. Search for "codeless kext" in the archives. HTH, - Fernando +++++++++ -- Xiaofan ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
