On Mon, 14 Mar 2005 16:34:57 +0100, Martin Paljak <[EMAIL PROTECTED]> wrote: > On Mon, 14 Mar 2005 15:51:08 +0100, Ludovic Rousseau > <[EMAIL PROTECTED]> wrote: > > - You don't need to use i2dw_be()/dw2i_be() since the value of > > IOCTL_FEATURE_VERIFY_PIN_DIRECT is "opaque" for the application. It is > > just 4 bytes and the byte order is not important. > I confirm that i'm lazy and thus stupid too. > I'm now somewhat ignorant as i'm too lazy to think but might it cause > problems if the application and actual reader ar eon different endian > machines ?
Good point. But I don't think it is a problem. if the driver and the application are on two different architectures (using a remote connection) the driver may write 1234 and the application will read 4321. But the application will then ask for the service 4321 and the driver will read 1234. So everything should be fine. > Wither way, what is needed in pcsc for this is the introduction of > SCARD_CTL_CODE > and the ability to send no data with SCardControl. Everything else can > be kept out of the scope of pcsclite. Needed tag codes can be kept > separately at ccid and application side if needed. I agree but since I am the maintainer of both pcsc-lite and the ccid driver it is best to make things clean from the start. Bye, -- Dr. Ludovic Rousseau For private mail use [EMAIL PROTECTED] and not "big brother" Google _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
