Hi Jim, the usermap format was defines in the modutils package many years ago. basically it has a flag at the beginning, and then a number of fields. only those with the bit set to 1 are checked.
all except one entry start with "openct 0x0003". copy one of those entries, and edit the second value (vendor) and the third (product). the others are ignored. if you enlarge your xterm a lot, you can see it beter (the lines are very long, but the first one line has the column headers). also, maybe your device is already matched by the generic ccid rule - bInterfaceClass = 0x0b bInterfaceSubClass = 0x00 bInterfaceProtocol = 0x00 lsusb -vv will show you if your reader has those values. > Bus 001 Device 005: ID 09c3:0008 ActivCard, Inc. SmartCard Reader > /root/testplug: usb > declare -x ACTION="add" > declare -x DEVICE="/proc/bus/usb/001/005" very good. I hope that file exists (i.e. /proc/bus/usb is mounted with an usbfs)? > declare -x PRODUCT="9c3/8/202" 202? as bcdDevice? strange, never saw a value other than zero here. not sure what it exactly means. but I think it is plain ignored. note: you can also debug your driver by running /usr/sbin/ifdhandler -H egate /dev/bus/usb/003/008 (add "-d" or "-dd" or ... for more debugging.) that can help to track down if there is an issue in the ifdhandler or in the hotplug stuff. and beware: if you ever update to dapper or later ubuntu version, they switched from hotplug to udev+hald and thus everything is different. I already updated the QuickStart page and other pages, but it still needs more work. Also ubuntu dapper no longer has /proc/bus/usb/ but instead /dev/bus/usb/ (and while you easily can have both it would cause problems - two processes running for the same device). Regards, Andreas _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
