Yes, the driver must set the "best" communication
settings from the ATR. But sometimes the card can do
more than it specifies on its ATR.
For instance Cryptoflex has D=1, F=372 on its ATR (the
default 9600 bps), but can do more baudrate if the
proper PTS is issued.
The driver can set the protocol/baudrate/BWT/CWT etc
based on the ATR, but the user (for instance a PCSC
Lite SSP) must have a way to request alternate
parameters, I think.
--- Jim Rees <[EMAIL PROTECTED]> escribió: > I think the
driver should take care of protocol
> selection, and choose the
> "best" available (highest speed, prefer T=1) without
> bothering the
> application with the details. That's how my
> Todos/PC3 driver is written.
> Does anyone agree with me?
>
***************************************************************
> 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
>
***************************************************************
__________________________________________________
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
***************************************************************
