On Fri, Apr 20, 2012 at 3:21 AM, Hans Petter Selasky <hsela...@c2i.net> wrote: > Hi Pete, > > I haven't followed the discussions on this list for a while. What's new with > libusbx? > > What API's are you changing?
Please refer to Pete's answer. Currently only libusb_get_version() call was added. http://libusbx.git.sourceforge.net/git/gitweb.cgi?p=libusbx/libusbx;a=shortlog > How do you plan to add support for FreeBSD 8 and later, which > has its own implementation of the official libusb 1.0 and 0.1. I think why FreeBSD 8+ has its own libusb-0.1 and libusb-1.0 implementation (on top of libusb20 library) is because of the desire to use BSD license. Am I right to assume that you will prefer FreeBSD 8+ libusb codes to be outside the libusb/libusbx project because of the licensing issue? If we look at the history of your libusb-1.0 compatible layer header, you follow closely with the libusb-1.0 API and add something which is not integrated to libusb-1.0 as well (USB 3.0 descriptor parsing). https://github.com/freebsd/freebsd-head/commits/master/lib/libusb/libusb.h I think you can continue doing that. If after a while, you want to switch to follow libusbx API, then you can participate in libusbx discussions and if you see a problem with a new proposed API, you can raise your concern. -- Xiaofan ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
