Hi,<br><div class="gmail_quote"><br>I am (well, not at the moment, but..) working on driver for vfs301, it is more or less operational - check out <a href="https://github.com/andree182/vfs301" target="_blank">https://github.com/andree182/vfs301</a> .<br>
<br><div class="gmail_quote"><div class="im">
On Sun, Feb 12, 2012 at 7:21 PM, Pierre Mauduit <span dir="ltr"><<a href="mailto:pierre.mauduit@gmail.com" target="_blank">pierre.mauduit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I have been provided by my company a dell vostro 3350 laptop last week,<br>
and I had to reformat the hard disk in order to install ubuntu. I lost<br>
the drivers and the windows app, thus I'm unable to snoop the usb<br>
traffic. The device is the following (relying on lsusb output) :<br>
<br>
Bus 002 Device 003: ID 138a:0011 DigitalPersona, Inc<br>
<br>
It seems that someone here already posted some usb snooping sessions, I<br>
wrote a python snippet which tries to mimic the urb sent to the device,<br>
but I'm a bit stuck with reverse engineering for now (the device on the<br>
capture files does not seem to be "plugged" at the same place as on my<br>
laptop - hypothetically bus 3 device 4 in the provided logs, bus 2<br>
device 3 on mine).<br>
<br>
- Is there a special windows app to install in order to be able to snoop<br>
the usb traffic ? I successfully installed the driver into a win seven<br>
virtualbox, but I could not manage to find a suitable software to use it<br>
concretely.<br></blockquote></div><div>For me "Usblyzer" was quite useful plus there were no problems with unsigned drivers in w7 x64.<br><br> </div><div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
- Is there anybody here currently working on the same device ? I tried<br>
to hack around the vfs101 driver with no luck, the initialization<br>
process does not look the same, and adding the vendorId / productId into<br>
the sources does not do the trick unfortunately. I got the following<br>
output, trying to use the enroll example:<br>
<br>
Scan your finger now.<br>
vfs101:error [async_recv_cb] seqnum mismatch, got 0401, expected 0000<br>
async:error [fpi_drvcb_enroll_stage_completed] BUG at async.c:161<br>
sync:error [fp_enroll_finger_img] unrecognised return code -5<br>
Enroll failed with error -22<br>
<br>
- Additionally, do you have some hints in order to get started with the<br>
current fprint code ?<br></blockquote></div><div><br>The preliminary version of vfs301 driver - the glue between the driver and libfprint - is as small as I could make it, so you could get some inspiration there. But no guarantees - I did not even post it to be merged into mainline yet...<br>
<br>Greetings,<br><br><br>--<br>Andrej<br></div></div>
</div><br>