On Mon, Mar 31, 2014 at 10:13 PM, Xiaofan Chen <[email protected]> wrote: > On Mon, Mar 31, 2014 at 9:24 PM, Paul Fertser <[email protected]> wrote: >> Thinking about it a bit more, I have a follow-up comment. >> To avoid mentioning codeless kexts and other obscure topics in README >> (e.g. I have no clue whatsoever about what that really means, sounds a >> bit like a windows "inf" file to me), and also since Darwin is an >> evolving kernel, wouldn't it be best if libusb project provided some >> official documentation regarding OS X in a clean and well-structured >> way, and OpenOCD docs would simply link to it? >> > > That is a good idea. I just updated libusb github wiki entry here. > https://github.com/libusb/libusb/wiki/FAQ#How_can_I_run_libusb_applications_under_Mac_OS_X_if_there_is_already_a_kernel_extension_installed_for_the_device > > Suggestions are welcome to make it better. You can link to libusb > github Wiki FAQ pages. > https://github.com/libusb/libusb/wiki/FAQ >
FYI, I have updated the FAQ after reading an article here. On the other hand, I think this method is more troublesome. So I think there is no need to update README.OSX file again. http://alvarop.com/2014/01/using-busblaster-openocd-on-osx-mavericks/ -- Xiaofan ------------------------------------------------------------------------------ _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
