On Tue, Oct 26, 2010 at 4:10 PM, Xiaofan Chen <xiaofanc@xxxxxxxxx> wrote:
> On Sat, Oct 23, 2010 at 8:02 PM, feng xiangjun <fengxj325@xxxxxxxxx> wrote:
>> first of all, it's not a regression (all kernels pre-2.6.36 not work either).
>>
>> I just tried to use an usb security key with 2.6.36.
>> It failed with message:
>>
>> usbhid 2-2:1.0: couldn't find an input interrupt endpoint
>
> And indeed your HID device has not interrupt endpoint. I am not
> so sure if this is a valid HID device or not. Some people seem
> to suggest that HID device needs to at least have an Interrupt IN
> endpoint. Last time we had a discussion in the libusb mailing list
> but I did not remember the final conclusion.
>
> Your HID device only uses the control endpoint for feature reports.
>
>> Yes, in windows, it can be accessed by a proprietary program.
>
> How does that program work? Is it a mini HID filter driver (like those
> mini filter for your mouse/keyboard/gamepad which is used together
> with a user space control program) or a user space program
> (using native HID API)? If it is a user space program, you can try to
> use libusb under Linux to simulate it.
The program is for online banking. It only runs in Windows.
The USB key is for login authentication.
I just tried using the program in qemu-kvm.
But due to the problem above, qemu-kvm can not even start.
When it probed usb device, it consumed %100 cpu(for ever) with the output
usb_create: no bus specified, using "usb.0" for "usb-host"
husb: open device 2.2
husb: config #1 need -1
husb: 1 interfaces claimed for configuration 1
husb: grabbed usb device 2.2
Thanks.
PS. my qemu command line:
qemu-system-x86_64 -hda img -boot order=c -m 512 \
-rtc base=localtime \
-usb \
-usbdevice tablet \
-usbdevice host:2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
