Le lundi 03 novembre 2003 � 10:17:54, Bettina Martelli a �crit: > Hello, Mr. Rousseau,
Hi Bettina, > He was also speaking about the GemPC433. > Is this reader also ccid compliant? I thought not. Yes, the GemPC433 is supported. Have a look at my CCID driver homepage [1] for a list of supported readers. > Smart cards > ----------- > CardOS/M3 (T=1) > CardOS/M4 (T=1) > Starcos SPK 2.3 (T=1) Since you use T=1 cards you have two options: - implement the T=1 protocol in TPDU in my CCID driver. But that may not be a good option - use a CCID reader working in APDU mode (instead of TPDU mode). My CCID driver support T=1 cards if the reader works in APDU mode (and does all the T=1 magic). Have a look at [2] and search readers working in APDU. Until now we have: - CardMan3121 - GemPC433_SL The GemPC Key and GemPC Twin do not tell they support APDU but they do. You just have to switch them (the code to switch them is commented in ccid-0.3.1/src/ccid.c) So the complete list of APDU mode readers is: - CardMan 3121 - GemPC 433 - GemPC Key - GemPC Twin > The GemPC410 works bad with CardOS and not at all with Starcos cards. What do yo mean by "works bad"? Maybe you can send me the bug description by private mail. > The requirement is that they should work in parallel, such that adding > a reader increases the throughput of heavy load operations like digital > signature. You will have to try Damien's pcsc-lite version for this. Regards, [1] http://pcsclite.alioth.debian.org/ccid.html [2] http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/Drivers/ccid/readers/?cvsroot=pcsclite -- Dr. Ludovic Rousseau [EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.musclecard.com/mailman/listinfo/muscle
