summaryrefslogtreecommitdiff
path: root/firmware/include/librfid
diff options
context:
space:
mode:
authorMin Xu <min.xu@min-info.net>2014-10-25 21:25:54 +0200
committerHarald Welte <laforge@gnumonks.org>2014-11-11 22:30:55 +0100
commit6bafd0cfb40c2d201f8723a3678dd4f04b380842 (patch)
tree5890ced84cb1ea633a700c443b35dcef46d9dfec /firmware/include/librfid
parent7e3c9959e1e140753738be9b6d4142f6c2068e3d (diff)
Don't split req_ctx with ATR payload
The codnition for flushing a req_ctx on UART idle is fixed to flush only if 1) There has been no new data since last check, and 2) There are no req_ctx currently pending to be transmitted to USB, and 3) We did NOT just got a reset and waiting for ATR I saw an ATR split in two different req_ctx prior, presumably flush decided to send req_ctx after ATR but got a new character just before sent). If we did get a RESET, let original logic decide to send the req_ctx -- presumably when ATR data is fully received.
Diffstat (limited to 'firmware/include/librfid')
0 files changed, 0 insertions, 0 deletions
personal git repositories of Harald Welte. Your mileage may vary