On Tue, Mar 12, 2013 at 10:05 PM, Xiaofan Chen <xiaof...@gmail.com> wrote: > As per his post to libusb-win32 mailing list, he will > probably drop libusb-1.0A support and use his own > USB implementation in the future. So I am not so sure > if your efforts will pay off that much. You could just > use his libusb-1.0A implementation for 1.5.1 and move > to his new things in the next version. > > Ref: > http://libusb.6.n5.nabble.com/add-device-port-number-usb-device-tp5711000p5711026.html > http://libusb.6.n5.nabble.com/add-device-port-number-usb-device-tp5711000p5711032.html > ++++++ > "Not much good to anybody else I imagine - libusb tries to > be everything to everybody, whereas my needs are more > focussed. But already having a API level over serial + usb + HID > meant that there was a degree of duplication that could be > eliminated. > > Ditched libusb, and replaced it with my own back ends, on Linux, > OS X and MSWindows (using libusb0.sys). Pretty much what everyone > else does anyway I guess, if they are not using a library like libusb. > > Graeme Gill" > ++++++++
As per the changelog, libusb support has been dropped since 1.5.0, so even if the libusb-1.0A codes are still there, I am not so sure whether they are supported by the upstream author (Graeme) or not. -- Xiaofan ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
