As I said before, usefulness is something relative, and sometimes, security is not a concern (even when talking about fingerprint readers). My intention with this is to try to create a catalog of fingerprint readers' properties and I think that taking a look at vendors' SDKs would be a good start. As pointed out by Greg, it would be also interesting to export those properties via sysfs instead of structure passing (or in addiction, not sure yet). I'm not sure though about relating fingerprint devices with V4L2 (even the cheapest ones). Some other considerations discussed with Greg are also: 1) extending those device informations to other classes, not only to fingerprint readers 2) maybe using another layer to hold device properties based on classes ( device driver -> device information layer -> sysfs+kobjects ) so we can have specific properties for "fingerprintreader" objects and easier ways to export them to the sysfs layer, without explicit declaration on the device driver 3) extend that layer also to non-USB devices ( bus-independent ) Maybe sysfs classes could have a list of default properties (for example, /sys/class/fingerprint objects could hold a list of commom fingerprint properties). Bill, which fingerprint reader are you using ? Daniel -- What this world needs is a good five-dollar plasma weapon. -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
