Dear Ludovic,

> I do not remember receiving merge requests from ACS. But my memory is
> not very good in the long term :-)
> Maybe the readers (or some of them) are not CCID compliant and then
> cannot be included in my driver.

Thanks for the clarification. This is a pitty vendors don't get in
contact with you.

> SCM (now IDentive) uses proprietary (non documented AFAIK) commands to
> talks to the contactless interface of their readers. Maybe they prefer
> to keep the command set secret and then provide their own proprietary
> driver.

Sorry, I meant SCM. Your answer is clear.

> I have no problem with people/company reusing my code as long as the
> licence is respected.

Perfect. There are two nice readers from ACS that may be worth looking
at. I mentioned these readers in a previous post. OpenSC users would
like very much to have access to small CCID PINPADs.
 
So I have two questions:

1) Do you think some code in libacs is worth backport to the main
libccid. They mention speed detection. But maybe other issues as well.
Did you make a diff and did you read libacs code? If ACS submits you a
patch, will you accept it?

2) On a different level, I wonder whether pinpad CCD display is managed
by libccid and/or by OpenSC. Is there support for CCD display in
libccid? Silly question!

Kind regards,
-- 
                  Jean-Michel Pouré - Gooze - http://www.gooze.eu

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to