Hello,
This is what I think I'm going to do with the PTS
issue:
* The driver will auto-set "best" comunication
protocol and speed, infered from the ATR, as explained
in previous e-mail.
* The CT-BCS command "Reset CT" will optionaly convey
the PTS request in it's data field. Note that this
behaviour will be optional, so it will not break
compatibility. This way if the application sends
20 11 01 01 00
where
CLASS = 20
INS = 11
P1 = 01 (functional unit = first ICC)
P2 = 01 (return complete ATR)
Le = 00
The driver will reset the card, select best
comunication settings (doing PTS if D!=1 F!=372 or > 1
protocol offered) and return the complete ATR.
But if the application sends
20 11 01 01 04 FF 11 11 FE 00
where
CLASS = 20
INS = 11
P1 = 01 (functional unit = first ICC)
P2 = 01 (return complete ATR)
Lc = 04
Data = FF 11 11 FE (Sample PTS request)
Le = 00
The driver will reset the card, perform the PTS
protocol and try set the communucation parameters as
specified in the PTS request.
The IFD handler will send this CT command in
SCardTransmit() when PCI != default protocol selected.
Does anybody sees something wrong in this design?
Thanks,
Carlos.
__________________________________________________
Do You Yahoo!?
Yahoo! Photos - Share your holiday photos online!
http://photos.yahoo.com/
***************************************************************
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***************************************************************
