On 2011-11-22 02:47, Marc-André Moreau wrote: > ...and pushed. > > I also refactored the code a bit according to the code style >
Thanks, I pulled it and it works now! I'm now looking into my next problem, which is that windows doesn't properly recognize the card readers features (i.e. pin pad and display in this case). I think this is supposed to work and that the problem is due to the following output: DBG_SCARD handle_Control (1016): Failure: Feature not supported. (0x8010001f) I dumped controlCode and it is 0x00313520 at this point. I found the following thread: http://lists.drizzle.com/pipermail/muscle/2006-April/005267.html which confirms that 0x00313520 is the windows variant of CM_IOCTL_GET_FEATURE_REQUEST and that the controlCode is not compatible across platforms (actually, it looks like it maps directly into an ioctl code so it makes sense that it's different). This is also suggested by the following comment in PCSC/reader.h: /** * Provide _source_ compatibility on different platforms */ #define SCARD_CTL_CODE(code) (0x42000000 + (code)) So obviously some magic needs to take place here, it can't just pass on the raw controlCode. Unfortunately I haven't yet figured out exactly how this magic should be implemented properly/cleanly. I guess the corresponding SCARD_CTL_CODE macros need to be studied in more detail. Maybe you have an idea? Regards, -- Christer Palm ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
