Le 19 février 2012 04:47, Godfrey Chung <[email protected]> a écrit : > Dear Jean-Michel Pouré > > 2012/2/18 Jean-Michel Pouré - GOOZE <[email protected]>: >> Le mercredi 08 février 2012 à 10:51 +0800, Godfrey Chung a écrit : >> libccid and libacsccid are installed. >> This is a Debian SID 64x station will all latest packages. >> >> * I plugged the APG8201-A1 for testing. It display "OK". >> When pugging the ACR83-A, nothing is displayed in the panel. >> Is this libacsccid role to display messages on the panel? > > No. > >> * How do I know whether my PINPAD is handed by libccid or libacsccid? >> In the case of the APG8201 it seems unclear to me, as it is listed in >> libccid "sould work" devices. > > You can see it from the debug log of pcsc-lite. > >> Should I uninstall libccid? > > I think you should uninstall libccid first. Actually, pcsc-lite will > load either libccid or libacsccid. It depends on how the system > returns the order of bundle directories.
Do you want me to remove support of ACS readers already supported by libacsccid to avoid conflicts? I have no problem with that. It would less support work for both of us. In "recent" versions of pcsc-lite if a reader is supported by 2 drivers then pcscd will select the specific driver instead of a "class" driver (defined by CCIDCLASSDRIVER in Info.plist). It is the case if you use udev hotplug. I think I added this mechanism during hal hotplug time. But if you use an "old" version of pcs-lite (or hotplug using libusb) you will not benefit from this mechanism. It looks like ACS has discovered this behavior since the ACS CCID fork has --no-class defined in its configure.ac. Bye -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
