John Chen wrote: > Peter, > Yes, you are right, this is a custom device, Here is the legacy code > to get the serial number > > if ( ::DeviceIoControl(m_hDeviceObject, IOCTL_EZUSB_GET_SERIAL_NUMBER, > NULL, 0, serial, cb, &cbOut, NULL)) > ... > do you know what I should do to map > the DeviceIoControl to libusb_control_transfer in this case?
That's a command to the Cypress generic driver for the FX2 chip. That generic driver converts this to a GET_DESCRIPTOR control message, exactly like the one in your code. I noticed the following lines in your log: > [ 0.159532] [000009c0] libusbx: debug [get_api_type] driver(s): WUDFRD > [ 0.160032] [000009c0] libusbx: debug [get_api_type] lower filter > driver(s): WINUSB So, it looks like this device has a UMDF driver, with WINUSB as a lower filter. Is libusbx trying to talk to this WINUSB instance? That is, does it assume that, if there is a WINUSB driver, it must be one it can chat with? -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ 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
