(In reply to comment #21) > (In reply to comment #20) > > Could you advice us which driver is good for reference, so that Arseniy > > could follow that one to rewrite it. > > There's no need to rewrite my driver, just minor changes here and there. > > > Or if Arseniy is unavailable to do it now, I can give it a try. > > I'm generally available, but Vasily has been somewhat impolite to me.
I'm very sorry if I was impolite to you, it wasn't intended. I'm just a bit tired of arguing why drivers MUST be asynchronous. I'll write a libfprint driver guideline when I get some spare time > Never > answered my question in comment #17, for example. Missed that one. Anyway: > Hang on. Don't you need a pointer to fp_dev to activate a device? And you only > get this pointer from fp_dev_open_cb callback, which callback is invoked after > all async transfers in dev_open are completed. Am I missing something? See img_dev_open(), it doesn't wait for any async xfers from dev_open(), only if you explicitly wait for async transfers to complete in dev_open() > That's why I'm not putting > too much effort into speeding up the process, simply because it's not > exactly fun. Heh > There is, however, fully asynchronous version of the driver: > https://bugs.freedesktop.org/attachment.cgi?id=77562. OK, will take a look tonight. Could you squash 2 patches into single meanwhile? Thanks! P.S. You still can catch me in IRC for faster communication... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790183 Title: [138a:0011] Fingerprint reader Validity Sensors not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/790183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
