aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristina Quast <chrysh.ng+git@gmail.com>2015-05-08 17:19:13 +0200
committerChristina Quast <chrysh.ng+git@gmail.com>2015-05-08 17:19:16 +0200
commit049772e68880e92558b2b94d8e8c9e4e90f14ca6 (patch)
tree21723e63d38f1696820deb3926f073cda33cf1ea
parent3b544a12177c1c996e61acc3be69c63818380f67 (diff)
phone.c: Removed comment about wait time extension
Wait time extension commands are not implemented yet. They are a nice-to-have for the future, since they would enable the board to work with phones that expect a higher frequency. With a wait time extension request towards the phone, SIMtrace could signal the phone to wait for a longer time period while SIMtrace is still waiting for a response from the SIM card.
-rw-r--r--firmware/src_simtrace/phone.c20
1 files changed, 0 insertions, 20 deletions
diff --git a/firmware/src_simtrace/phone.c b/firmware/src_simtrace/phone.c
index 0ea3a33..a455557 100644
--- a/firmware/src_simtrace/phone.c
+++ b/firmware/src_simtrace/phone.c
@@ -53,26 +53,6 @@
/// The USB device is in resume state
#define STATE_RESUME 5
-/* WTX (Wait time extension):
-* R-block PCB begins with (msb) 10 , ends with 000011 for WTX req, 100011 for WTX resp
-*
-* The standard says:
-* Rule 3 β€” If the card requires more than BWT to process the previously received I-block, it transmits S(WTX
-* request) where INF conveys one byte encoding an integer multiplier of the BWT value. The interface device
-* shall acknowledge by S(WTX response) with the same INF.
-* The time allocated starts at the leading edge of the last character of S(WTX response).
-*/
-// FIXME: Two times the same name for the define, which one is right?
-//#define WTX_req 0b10000011
-//#define WTX_req 0b10100011
-// Alternatively:
-/* For T = 0 Protocol: The firmware on receiving the NULL (0x60) Procedure byte from the card, notifies
-it to the driver using the RDR_to_PC_DataBlock response. During this period, the reception of bytes
-from the smart card is still in progress and hence the device cannot indefinitely wait for IN tokens on
-the USB bulk-in endpoint. Hence, it is required of the driver to readily supply β€˜IN’ tokens on the USB
-bulk-in endpoint. On failure to do so, some of the wait time extension responses, will not be queued to
-the driver.
-*/
extern volatile uint8_t timeout_occured;
/*------------------------------------------------------------------------------