NOTE: Message resent due to message size limit. The original attachment may be found at: http://skandalfo.dyndns.org:9999/hp/UPEK_capture.tar.bz2
Hi, Daniel and everyone else. I own an Acer laptop sporting an unsupported UPEK swipe-type fingerprint reader device. Its lsusb info is this: Bus 006 Device 002: ID 147e:1000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x147e idProduct 0x1000 bcdDevice 0.33 iManufacturer 1 TouchStrip iProduct 2 Fingerprint Sensor iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 10 Device Status: 0x0000 (Bus Powered) It seems to be some variation of the TouchStrip thing. As it is supported by the 32 bit BSAPI binaries, I enclose a .tar.bz2 with a series of captures: - open_1 and open_2 are the snoops of the Biometry sample application "opening" the device, which I think should be considered as the initialization steps. I looked a bit inside the upeksonly driver, and I think the snooped sequence is some kind of superset of the upeksonly one. - close_1 and close_2 are the snoops of the Biometry application closing the respective open_N sessions. - add_1 and add_2 are complete enrollments. - add_pre_1 is an incomplete enrollment. I'm not sure about whether the snoop includes data after the enrollment timed out with no finger detected. - add_pos_1 is the second part of a successful enrollment (starting after the application has begun waiting for a finger). - verify_2 is a successful and complete verification of a fingerprint. - verify_pre_1 is a pre-finger part of a successful verification. - verify_pos_1 is a finger-to-end part of a successful verification. I hope this information helps you guessing how this device works. It is the last unsupported device on my laptop after I contributed an infrared port driver (wpc8769l) to LIRC and Antti Palosaari wrote another (ce6230) that can drive the integrated AVerMedia A310 DVB-T tuner. If the device operation happens to be easy to ascertain, I myself could write a driver or extend the upeksonly one (given I find the required time). Best regards, and thanks in advance, Juan Jesus Garcia de Soria. -- Dream small if success is enough for you; dream big if you need to change the world. _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
