Carlos and devs, I saw your email. The development group is probably working a full load as it is. I was hoping someone was working on a similar model, and that I could run tests and dump data out for them to see and possibly give me direction on things I could do to help bring this scanner under one of the drivers. I could do some coding also. It's what I do. I don't do much currently, in fact none, in the way of writing device drivers. However, I do know *how* to write Linux device drivers for the 2.6 kernel. I'm not looking to jump in all cold turkey and do it all by myself, but if someone were to give me some directions and tasks to complete I would be more than willing to tackle the task of working with someone in adding this to an existing driver, or create a new one by forking an existing driver for this scanner.
However, without knowing which driver might possibly be compatible and which one could be stripped down to a basic shell to begin exploring the capabilities I am unwilling to risk damaging it. Yet. It would be nice to know who really makes the chip, but this is my business laptop, so I will not be hacking this one by disassembling and dissecting and/or modding. At least not until the warranty is up and I am left with no other choice. Doing things at a driver development level I am willing to risk, within reason. I wiped Windows Vista from the laptop, so can't test in Vista. I did keep the emergency restore partition, and might be able to restore Windows Vista to some portion of the disk (or more likely - have it wipe my Linux install and have to restore from a backup). If that was needed for testing purposes. I have not seen a response to my offer to help develop a driver for this and know scratch about fingerprint readers, so I really have no good answer for your question. I will attempt one anyway. Having pictures of the guts of the device would be a starting point. That would show the chip(s) involved and then getting the specs for the chips involved would be the next stage. Getting the specs for the chip(s), may be the tough part. It is essential to find out the capabilities of the chip(s). Once that is known writing the driver should be relatively easy. Brian On Tue, April 26, 2011 4:33 am, Carlos Vedovatti wrote: > Hi Brian, > > ... > I wanted to ask you if you have any idea > of what information is needed from the Validity Inc. to develop a > driver? or we just wait until someone comes with a idea, information, > etc.? > > Basically I wrote to Validity Inc. to see if they could provide > something ... > > Carlos Vedovatti > _______________________________________________ fprint mailing list [email protected] http://lists.reactivated.net/mailman/listinfo/fprint
