> What are the requirements a SmartCard user has to his/her interface: > > - switching on/off the interface > - detecting if a SmartCard is plugged in > - resetting the SmartCard > - locking the SmartCard > - setting up the communication parameters like FI/DI/convention > - activating the clock stop mode (to save power) > - anything else?
The list gets longer: Jim Rees wrote: > You might want to add pinpad support. Also think about how you want to > handle multiple readers or multiple slots per reader. And card > insert/removal notification. 'pinpad' means a reader's local keyboard? Does it require some kind of communication between the SmartCard and the application? Or handled locally in the reader device? 'Multiple readers/multiple slots': My i.MX25 processor provides two independent SmartCard interfaces. Are these two physical interfaces "multiple readers" or more like "multiple slots"? BTW: Are there any preferences how to communicate with the kernel driver? It could be done via IOCTLs (the classic way) or via sysfs entries. Just an idea: Via sysfs it would be possible to create named entries in a per hardware feature. So, only entries exists the hardware really supports. A userland application (or openct/PCSC adaption driver) would be able to detect hardware's features by scanning the sysfs entries. Regards, Juergen -- Pengutronix e.K. | Juergen Beisert | Linux Solutions for Science and Industry | Phone: +49-8766-939 228 | Vertretung Sued/Muenchen, Germany | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de/ | _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
