Hi, On Monday 25 December 2006 14:14, Ludovic Rousseau wrote: > On 25/12/06, Martin Preuss <[EMAIL PROTECTED]> wrote: > > On Sunday 24 December 2006 21:39, Ludovic Rousseau wrote: > > > On 24/12/06, Martin Preuss <[EMAIL PROTECTED]> wrote: [...] > I see. Strange. The driver is loaded for the first reader so it may > corrupt pcscd memory and trash the reader name. It may also be a bug > in pcsc-lite. [...]
After looking at your driver again I added handling code for some tags, especially TAG_IFD_SIMULTANEOUS_ACCESS, TAG_IFD_THREAD_SAFE, TAG_IFD_SLOTS_NUMBER and TAG_IFD_SLOT_THREAD_SAFE (BTW: I also added handling of your new tags for IFD version and vendor name). *Now* my driver is called with the correct LUN values (00000, 10000, 20000 etc). While this solves my problems the handling of defaults by the pcsc daemon seems a little bit odd to me: I guess the daemon should under no circumstances call the same driver with an already in-use LUN for different readers, because there is no useful way for the driver to react but rejecting such a request (because in susequent request like IFDHICCPresence the driver could not determine the destination reader for the request). Anyway, thanks for your help (and your clean driver which always serves as a reference implementation and which also helped me a lot while developing my own projects). Regards Martin -- "Things are only impossible until they're not" AqBanking - http://www.aqbanking.de/ LibChipcard - http://www.libchipcard.de/ _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
