2010/5/20 Juergen Beisert <j...@pengutronix.de>: > Andreas Jellinghaus wrote: >> I think >> - read data >> - write data >> - warm reset >> - hard reset >> - get card status (card / no card / card removed and added again)
You will also need a way to get card events: a card has been inserted, a card has been removed. Or you will have to do polling using the "get card status" Also think about a way to get reader events: a reader has been connected, a reader has been removed. But maybe your reader will be always connected so you do not need this. >> oh, add ejectif you have a physical way to eject a card. or sensors that >> tell you if a card is properly inserted, detected as fake, has a wire to >> outside of the atm preventing some gate to close behind the card and >> whatever. > > I saw other readers are also able to lock the card. Also a useful case? Never used or seen such a reader. And PC/SC does not know how to use this feature AFAIK. Do not over design your protocol. But make it expandable. Bye -- Dr. Ludovic Rousseau _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
