Purchase ISO 7816 parts 3 and 4 to understand the low level communication
between card and IFD (Terminal, card reader).

Peter T
Bristol UK
----- Original Message -----
From: "Joe Phillips" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Wolf Geldmacher" <[EMAIL PROTECTED]>
Sent: Thursday, August 02, 2001 3:43 AM
Subject: MUSCLE GPR400 ifd and T=0 vs T=1 from the driver perspective


>
> I've got a mostly working GPR400 PCSC IFD.  It's based on the PCMCIA
> driver found in the card-0.9.6.tar.gz file found on the MUSCLE website.
>
> By 'mostly working' I mean that I've used formaticc to send a few APDUs
> to a card and received the expected results.
>
> I'm having troubles understanding what the differences are between T=0
> and T=1 from the IFD developer perspective.  It's not apparent to me
> from looking through the other IFD source files.
>
> I have the Smart Card Developer's Kit and Java Card Technology for Smart
> Cards books already.  I understand that T=0 and T=1 are two different
> protocols for communication between the reader and the card.  It is not
> clear to me *how* they are different other than "one is byte oriented
> and the other is block oriented."
>
> Can anyone offer any insight into the differences, if possible, from the
> IFD developer perspective?  Can you point me to some documentation
> and/or code that will clear this up for me?
>
> Thanks in advance.
>
> -joe
>
> ***************************************************************
> Unix Smart Card Developers - M.U.S.C.L.E.
> (Movement for the Use of Smart Cards in a Linux Environment)
> http://www.linuxnet.com/
> To unsubscribe send an email to [EMAIL PROTECTED] with
> unsubscribe sclinux
> ***************************************************************
>

***************************************************************
Unix Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/
To unsubscribe send an email to [EMAIL PROTECTED] with
unsubscribe sclinux
***************************************************************

Reply via email to