I have one device called "entropy key" http://www.entropykey.co.uk/
9: USB 00.0: 10200 Modem
[Created at usb.122]
Unique ID: hhw5.xbUS5LcXf33
Parent ID: FZIx.RTX9xWW_uz4
SysFS ID: /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0
SysFS BusID: 8-1:1.0
Hardware Class: modem
Model: "Simtec Electronics Entropy Key"
Vendor: usb 0x20df "Simtec Electronics"
Device: usb 0x0001 "Entropy Key"
Serial ID: "M/9uBjBLNzE3QSFD"
Driver Modules: "cdc_acm"
Device File: /dev/ttyACM0
Device Files: /dev/ttyACM0,
Speed: 12 Mbps
Module Alias: "usb:v20DFp0001d0200dc02dsc00dp00ic02isc02ip01"
Driver Info #0:
Driver Status: cdc_acm is active
Driver Activation Cmd: "modprobe cdc_acm"
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #18 (Hub)
which works just fine most of the time, except that it has never-ever
recovered after suspend/resume, the only way to make it "live again" is
plug/unplug the device after resume, or with an pm script
case "$1" in
and well, that's really *really* ugly.
Looking at the USB quirks list, looks like this device needs
USB_QUIRK_RESET_RESUME, I am not a kernel developer so Im not sure about
if this is correct.
will be cool if someone can add the quirk if it is the correct one or
point me to the right approach. ;)
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org