Marius,
And it would help to know if the Opencard implementation is the
ISO or EMV version, or whether the differences are expected to be
dealt with by purchasing the reader/writer and the cards as
matched sets, i.e. whether the parts that are different are
implemented in the reader/writer. (The differences are in the error
handling and some of the ATR parameter fields, and the
reader/writer cannot find out from the card which version it has
implemented.)
Regards
Peter Tomlinson
Iosis, 4 Sommerville Road, Bristol BS7 9AA, UK
[EMAIL PROTECTED]
From: Marius Schilder <[EMAIL PROTECTED]>
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Subject: [OCF] T=1
Date sent: Fri, 9 Jul 1999 09:45:27 -0700
> Hi,
> suppose my custom card uses T=1 but not the APDU commands, can the opencard
> implementation of T=1 terminal side deal with that? What API is exposed to
> just send & receive blobs? Preferably the chaining and other T=1 issues are
> resolved by the driver.
>
> marius
> Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
> access to documentation, code, presentations, and OCF announcements.
> -----------------------------------------------------------------------------
> To unsubscribe from the OCF Mailing list, send a mail to
> "[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
> message.
>
Visit the OpenCard Framework's WWW site at http://www.opencard.org/ for
access to documentation, code, presentations, and OCF announcements.
-----------------------------------------------------------------------------
To unsubscribe from the OCF Mailing list, send a mail to
"[EMAIL PROTECTED]" with the word "unsubscribe" in the BODY of the
message.
