Re: [Libusbx-devel] Getting config descriptor 0 fails on Windows

2012-11-21 Thread Bas van Dijk
Thanks for the info Pete! On 21 November 2012 23:15, Pete Batard wrote: > On 2012.11.21 18:41, Bas van Dijk wrote: >> libusbx: warning [hid_open] could not open HID device in R/W mode >> (keyboard or mouse?) - trying without > > If libusbx gives you a warning, you're supposed to pay some attentio

Re: [Libusbx-devel] Windows: libusb_claim_interface fails on 1.0.13 and higher

2012-11-21 Thread Pete Batard
On 2012.11.21 05:38, Xiaofan Chen wrote: > Another round of Google finds the HID report descriptors. > http://www.protonbasic.co.uk/showthread.php/64764-USB-CDC-HID-IAD-interface > > So it does not have multiple HID collections. Yeah. 46D is Logitech's VID, and Microchip is 4D8. I misread the log

Re: [Libusbx-devel] Windows: libusb_claim_interface fails on 1.0.13 and higher

2012-11-21 Thread Pete Batard
On 2012.11.21 05:19, Xiaofan Chen wrote: > I remember that the Windows HID backend does not yet support > HID Collections. Is this still true since it is not listed in the known > restrictions. Good point. It's the same code as before, so the same restrictions apply. I've updated the wiki. Regar

Re: [Libusbx-devel] Getting config descriptor 0 fails on Windows

2012-11-21 Thread Pete Batard
On 2012.11.21 18:41, Bas van Dijk wrote: > libusbx: warning [hid_open] could not open HID device in R/W mode > (keyboard or mouse?) - trying without If libusbx gives you a warning, you're supposed to pay some attention to it... :) >VID:PID: 0627:0001 Let's see 0627 = Adomax Technol

Re: [Libusbx-devel] Getting config descriptor 0 fails on Windows

2012-11-21 Thread Bas van Dijk
Note that this is on a virtual Windows 7 PC: C:\Users\Bas\Downloads\libusbx-1.0.14-win\examples\bin32>listdevs 8086:7020 (bus 1, device 1) 0627:0001 (bus 1, device 2) C:\Users\Bas\Downloads\libusbx-1.0.14-win\examples\bin32>xusb.exe 8086:7020 Using libusbx v1.0.14.10576 Opening device 8086:7020..