Hi! > you can define/use vendor specific features if you want to I guess that this will be often used by vendors. The sharing of a header file which defines IOCTL's between a driver and applications can't be circumvented here; because it would be the same on Windows and because applications which need these IOCTL's are very often provided by the same vendor and/or included in SDK's this should be no problem. > It is not mandatory for your application or your driver to #include > <PCSC/reader.h> but it should be convenient As only certain PC/SC-'client' software will use the IOCTL's this is fine, with the exception that the SCARD_CTL_MACRO should be included via the winscard.h in some way: getting the SCARD_CTL_MACRO on Windows via winscard.h and on Linux via reader.h (or however it is called then) is confusing! > the file PCSC/reader.h will be provided by pcsc-lite since I have no > better idea Adding the other IOCTL's definitions then to reader.h is okay for us, but I consider that the final PC/SC standard may want to see these definitions again in another place. This is also way we sayed that it would be sufficient to define the SCARD_CTL_MACRO in pcsc-lite headers from beginning, in order to ensure a consistent control code generation, maybe add the SCARD_CTL_CODE(3400) and delay the rest until the PC/SC standard is finished. -- Best regards, Markus Hofer OMNIKEY Ferihumerstrasse 13 A-4040 Linz Austria Tel +43 (0) 732 / 602220 - 30 Mobile +43 (0) 664 / 1106386 Fax +43 (0) 732 / 602220 - 15 E-Mail [EMAIL PROTECTED] Web www.omnikey.com _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
