Pete Batard wrote: > I have now pushed a patch that adds libusb0.sys and libusbK.sys > support there, for testing.
I look forward to some testing! Even if it comes at the cost of the libusbK DLL it's still very nice that libusb-1.0 code can be used with the libusb-win32 driver. > To fetch the branch: > > git clone git://github.com/pbatard/libusbx.git libusbx-pbatard > cd libusbx-pbatard > git checkout 0K > > Note that because the branch is not off mainline, but off a personal > libusbx repo, you must go through a new clone. Both branches (master and 0K) in your personal repo have parents on libusbx.git master, so I suggest for everyone to simply add a remote and fetch from that in their existing worktrees, rather than making new clones. Repositories don't matter at all, only commits matter. > I should also point out that the implementation is very dependent on > the KUSB_FNID definitions from libusbK and their order, This seems fragile. Is there any more robust way? > The one minor issue I found is that I get the following in xusb when > trying to fetch the string descriptors of an XBox Controller device, > when libusb-win32 is used: > > Reading string descriptors: > libusbx: error [winusbx_submit_control_transfer] ControlTransfer failed: > [31] A device attached to the system is not functioning. > > That device doesn't have strings, so this is not a major issue, and the > libusb0 driver doesn't seem to have an issue returning strings for > devices that have them. It's just in case there are no strings that > libsusb0 seems to differ from the others and produces an error whereas > the other drivers don't complain. Interesting. Is the error definitely coming from the libusb0 driver, as opposed to libusbK? Which string descriptor is being read from the device by the way - because if there are no strings then all iFoobla descriptor fields should be 0, and then there will also be no descriptor 0, so then I would certainly expect an error for the control transfer. (Though the error code is a little surprising.) Did Travis help with this code too, besides libusbK providing WinUSB compatibility? This is a nice feature, so I think he deserves credit! Thanks, //Peter ------------------------------------------------------------------------------ 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
