Hi,
Zitat von Godfrey Chung <godfrey.ch...@acs.com.hk>:
Yes, libccid works for a few models only while libacsccid works for
all models of ACS CCID smart card readers.
You can download the drivers from
http://www.acs.com.hk/index.php?pid=drivers. For example, select
ACR122U (http://www.acs.com.hk/index.php?pid=drivers&id=ACR122U) and
you will find the driver
(http://www.acs.com.hk/drivers/eng/ACR122U_driver_Lnx_Mac10.5_10.6_1.02_P.zip). The driver "acsccid-1.0.2.tar.bz2" is in the zip
file.
I am a maintainer of the driver. acsccid-1.0.2 is based on
ccid-1.3.11 and supports all models of ACS CCID smart card readers.
The driver is tested by software and hardware engineers from ACS.
I figured from your mail address that ACS is directly involved here.
OTOH, why are those changes not pushed to libccid upstream? For
generic protocols like CCID (where even Windows has a generic driver
for it), there should not be a driver set for each vendor, it simply
defeats the purpose of generic protocols like that.
Your example of ACR122U is marked as "should work" at
http://pcsclite.alioth.debian.org/ccid/iManufacturer.html#2
If the libccid upstream is not cooperative for including your changes
(if it's done in a clean way), maybe you can work with the Debian
libccid maintainer?
HS
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
