lets probe our understanding of CCID compliance, re escape command.
"When a CCID doesn't declare the values 00000010h and 00000020h," in the features element of the CCID descriptor,
then
"the frequency or the baud rate must be made via manufacturer proprietary PC_to_RDR_Escape command."
Surely, this work must be performed by the driver. It can know from the ATR (perhaps) which manufacturer's device it is negotiating PPS with. Thus, the driver must know the set of proprietary commands it MUST send, to be conforming.
While this reasoning is correct, its impractical if we are distributing platform-level drivers.
Using SCardControl to pass control back to the application, so it can indicate the required proprietary commands, seems practical.
----- Original Message ----- From: "Ludovic Rousseau" <[EMAIL PROTECTED]>
To: "MUSCLE" <[EMAIL PROTECTED]>
Sent: Thursday, November 11, 2004 6:39 AM
Subject: Re: [Muscle] SCardControl / GlobalPlatform support / ImplementationofService Providers
Le Thursday 11 November 2004 � 06:10:40, Peter Williams a �crit:Would you see using SCARDCONTROL similarly for the PC_To_RDR_ESCAPE CCID PDU ?
Do you mean something like [1]? Of course you will have to use a compliant driver like my CCID driver.
Bye,
[1] http://pcsclite.alioth.debian.org/pcsc-lite/node27.html
-- Dr. Ludovic Rousseau [EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- _______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
_______________________________________________ Muscle mailing list [EMAIL PROTECTED] http://lists.drizzle.com/mailman/listinfo/muscle
