Re: pcscd support for Class 2 SPE for Cherry SmartBoard xx44
Ludovic Rousseau <[email protected]>
| Newsgroups | gmane.comp.lib.muscle |
|---|---|
| Message-ID | <CAGstE8BTZyPcZiyvMZHfHr3J4svLQQrk2+ENFgMenrnzrifXwg@mail.gmail.com> |
2013/8/23 Martin Paljak <[email protected]>: > On Thu, Aug 22, 2013 at 11:02 PM, Ludovic Rousseau > <[email protected]> wrote: >> The ControlCode: 0x313520 is not know and the application get an error code. >> >> From [1]: >> " Thanks again: you were correct on the control code (SCARD_CTL_CODE(3400) = >> 0x42000D48 under Linux and 0x313520 under Windows) issue: I do get my list of >> features now " >> >> Are you using a remote desktop application with a Windows application >> running on a server? > > But isn't the only solution in this case to have "binary > compatibility" AKA same magic constants? It would be the perfect solution. But the value of SCARD_CTL_CODE(3400) is not documented anywhere. So I had to chose one. Yes, I could have written a Windows program to get the value under Windows. But I do not use Windows. > For sake of compatibility > with remote desktop clients maybe even supporting two base constants > in parallel would make sense ? I think it is the job of rdesktop and other RDP clients to convert the values between the 2 worlds. I just added support of the windows value 0x313520 in the CCID driver revision 6739. But the problem should be elsewhere since the same application worked with pcsc-lite 1.6.4. Bye -- Dr. Ludovic Rousseau