Yes, we track the changes on every libccid release and update back to
acsccid release if the changes are correct. Starting from libccid 1.3.11, we
found that libccid blacklisted our best selling reader "ACR122U" of some
firmware versions (< 2.06). Therefore, it made our customer getting into
trouble and created a storm of customer complaints. We introduced them to
use our officially supported driver.
Starting from libccid 1.3.12, we found that it did not maintain backward
compatibility. The users are required to upgrade pcsc-lite to 1.6.x and
libusb to 1.0.x. We have a lot of customer using old Linux distributions and
these required components will not be ported. We must maintain our quality
standard and customer satisfaction. However, acsccid can be used with
pcsc-lite 1.3.3 - 1.7.x and kept to use libusb 0.1.x. We also consider to
use libusb 1.0.x on future release but the driver will be modified to use
either libusb 0.1.x or libusb 1.0.x to maintain backward compatibility. Next
release of our driver also include ACS non-CCID readers support.
Godfrey
-----Original Message-----
From: Hendrik Sattler
Sent: Wednesday, May 18, 2011 4:48 PM
To: Godfrey Chung
Cc: 627...@bugs.debian.org ; debian-devel@lists.debian.org ;
rouss...@debian.org
Subject: Re: Bug#627038: ITP: libacsccid -- PC/SC driver for ACS USB CCID
smart card readers
Zitat von Godfrey Chung <godfrey.ch...@acs.com.hk>:
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.
But libccid evolves and forks of such projects do usually not follow.
This leaves both in a rather sad situation. Did you track the changes
of 1.3.12 and 1.3.13? Any intention to rebase the work on 1.4.x so
libusb-1.0 gets used instead of libusb-0.1?
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.
The Windows driver is also not very standard-compliant and does nasty
things. It took me 30min on XP and Vista to get a bluescreen from it :-/
Note that there is also libusb-win32, making it potentially possible
to use the same source there (ignoring the Microsoft driver for it)
once it is compatible with (or integrated into) libusb-1.0.
Please note that libccid upstream author and Debian maintainer are same
person. He may reject our changes.
Let's CC him so that he can comment...
HS
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/E6EBDFA9262B4D578EE6E6AE3EAC0E9F@GODFREYPC
