[Pcsclite-cvs-commit] r4510 - /trunk/Drivers/ccid/src/defs.h

[rousseau at users.alioth.debian.org]

Author: rousseau
Date: Sun Oct 25 19:14:10 2009
New Revision: 4510

URL: http://svn.debian.org/wsvn/pcsclite/?sc=1&rev=4510
Log:
change CMD_BUF_SIZE to support extended APDU of up to 64kB. We need this
size for readers in APDU mode to be able to receive the card response in
one block (chaining is not always possible in this direction)

Modified:
    trunk/Drivers/ccid/src/defs.h

Modified: trunk/Drivers/ccid/src/defs.h
URL: http://svn.debian.org/wsvn/pcsclite/trunk/Drivers/ccid/src/defs.h?rev=4510&op=diff
==============================================================================
--- trunk/Drivers/ccid/src/defs.h (original)
+++ trunk/Drivers/ccid/src/defs.h Sun Oct 25 19:14:10 2009
@@ -66,16 +66,9 @@
 /* Flag set when a power down is requested */
 #define MASK_POWERFLAGS_PDWN 0x02
 
-/* Kobil readers does not support APDU chaining for T=1 so you can't send an
- * extended APDU. The readers supports a command of up to 512 or 420 bytes.
- * For a Kobil KAAN Base/advanced reader you should use
- *  #define CMD_BUF_SIZE 420
- * For the other models you should use
- *  #define CMD_BUF_SIZE 512
- * Kobil is aware of the problem and do not plan to solve it.
- */
-/* Communication buffer size (max=adpu+Lc+data+Le) */
-#define CMD_BUF_SIZE (4+1+256+1)
+/* Communication buffer size (max=adpu+Lc+data+Le)
+ * we use a 64kB for extended APDU on APDU mode readers */
+#define CMD_BUF_SIZE (4 +3 +64*1024 +3)
 
 /* Protocols */
 #define T_0 0