Hello Pete > Sure, and there is an implementation, but the implementation needed > further work before being added into the Windows backend and the > author didn't work with Pete on that. > > My http://git.stuge.se/?p=libusb-stuge.git;a=shortlog;h=libusb0 branch > has two snapshots of the downstream "fork" of libusb which includes > the code for the Windows backend to use the libusb0.sys kernel driver. > > This is not the cleanest code you have seen, otherwise it would of > course be in libusb and thus also libusbx already. YMMV, but it's a > start, and the author does use it in his application. > > For further work it's also a problem that there are so many unrelated > changed in the commits, but well, nothing much to do about that > except to clean it up. I've inserted a commit to remove the unrelated > changes and have pushed that into a libusb0-cleanup branch, this > makes it easier to get an overview of the changes against master, but > forward porting the code of course still remains, and in that process > I think some refactoring is required for the duplicated code. >
Sweet. I assume this is going to be OK on x64 (perhaps eventually :). Is there a plan for code signing? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
