[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers



Before we started the driver project in 2009, we had requested to join as a developer for libccid in alioth.debian.org but the author rejected us with no reason. As the same time, our customer pushed us to release Linux driver. Therefore, we decided to release our Linux driver based on libccid and had a plan to release our driver to any Linux Distributions.

For the Windows platform, we also release our own driver. It is because the generic driver does not work with multi-slot smart card readers and we can control our driver source code to fix bugs from the readers.

Please note that libccid upstream author and Debian maintainer are same person. He may reject our changes.

Godfrey

-----Original Message----- From: Hendrik Sattler
Sent: Wednesday, May 18, 2011 3:46 PM
To: Godfrey Chung
Cc: 627038@bugs.debian.org ; debian-devel@lists.debian.org
Subject: Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID smart card readers

Hi,

Zitat von Godfrey Chung <godfrey.chung@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



Reply to: