On 15/11/06, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
On 14/11/06, Andreas Jellinghaus <[EMAIL PROTECTED]> wrote:
> does it expose this to opensc, so we can set max_recv/send_size
> accordingly?
No. But I can do that.
As I said in a previous message, the CCID driver can expose this
reader limitation using a PC/SC call to SCardGetAttrib(..,
SCARD_ATTR_MAXINPUT, ..) to let the application know the maximum input
size (the SCardGetAttrib() call is made by the application). This
would be transparent for pcsc-lite.
The problem is I don't know if SCARD_ATTR_MAXINPUT can be used for
that. Does anybody have a documentation of the Microsoft SCARD_ATTR_*
commands?
I added support of SCARD_ATTR_MAXINPUT in my CCID driver in revision
2197 [1] and a test for that in testpcsc.c in revision 2198 [2].
This will be included in the next stable CCID driver version.
The size is returned as a uint32_t. I do not use int to avoid problems
on a 64-bits system with a 64-bits CCID driver and a 32-bits
application (or the reverse). See also pcsc-lite bug #303790 [3] on
that.
Bye,
[1]
http://lists.alioth.debian.org/pipermail/pcsclite-cvs-commit/2006-November/002356.html
[2]
http://lists.alioth.debian.org/pipermail/pcsclite-cvs-commit/2006-November/002357.html
[3]
https://alioth.debian.org/tracker/index.php?func=detail&aid=303790&group_id=30105&atid=410085
--
Dr. Ludovic Rousseau
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
