Fwd: 2.6.36: couldn't find an input interrupt endpoint

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Oct 24, 2010 at 12:42 AM, Greg KH <greg@xxxxxxxxx> wrote:
> On Sat, Oct 23, 2010 at 08:02:58PM +0800, feng xiangjun wrote:
>> Hi, everyone.
>>
>> 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
>>
>> The same key can be used in Windows XP SP2 with no special driver,
>> so I assume that Linux can use it.
>
> Not really, odds are a userspace program attaches to this device in
> Windows, right? ÂHow do you interact with it?

Yes, in windows, it can be accessed by a proprietary program.
I just tried using it in qemu-kvm-0.13.0 with the same program.

But qemu-kvm can not 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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux