summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlaforge <laforge@e0336214-984f-0b4b-a45f-81c69e1f0ede>2006-10-25 23:33:21 +0000
committerlaforge <laforge@e0336214-984f-0b4b-a45f-81c69e1f0ede>2006-10-25 23:33:21 +0000
commitc972071a03825d8fe595d33f9128b4341b0478bd (patch)
tree8ef7a9d18c221947f32e2f4426208aa1943676a7
parentbbb902ddc903f9e6f7bb3dbdbf9a5a237f09a90b (diff)
update TODO
git-svn-id: https://svn.gnumonks.org/trunk/librfid@1917 e0336214-984f-0b4b-a45f-81c69e1f0ede
-rw-r--r--TODO22
1 files changed, 20 insertions, 2 deletions
diff --git a/TODO b/TODO
index 9bc889b..649fb96 100644
--- a/TODO
+++ b/TODO
@@ -1,5 +1,7 @@
rc632:
- fix handling of timeout (program timer of RC632)
+- add a timeout tolerance factor that can be user-specified
+- make sure interrupt mode for timer wait works
cm5121:
- fix handling of TX or RX > 0x7f [buffer length in atmel chip?]
@@ -16,10 +18,12 @@ iso15693:
- implement all the rest
mifare_clasic:
+- test
+- try to auto-detect 1k/4k
+- try to distinguish mifare ultralight and mifare classic in/after anticol
tcl:
- implement pps for asymmetric (rx/tx) speeds
-- test pps
openct:
- add ifdhandler driver
@@ -27,4 +31,18 @@ openct:
other:
- implementation of code for various passive tags
- documentation
-
+- add notion of 'asic implementation' for specifying reader-specific
+ initialization values such as mod_conductance
+- abstract a read single block / read multiple block API where l2/proto
+ layer can provide multi-block function (e.g. iso15693), which will be
+ emulated in case there only is a single-block function
+- switch over to use of rfid_buf structure, similar to linux skb. upper
+ layers have sufficient headroom in order to have lower layers add protocol
+ headers in front of a packet
+- implement software checksumming support. The reader should be able to
+ indicate whether it supports hardware checksum generation / verification.
+- application software should be able to override hardware csumming on request
+- implement some auto-calibration mode where the user is requested to leave a
+ single PICC/VICC on the reader and the software iterates through various
+ mod_conductance and bitphase values to see whether it can calibrate to a given
+ [new] card. The resulting calibration values are printed by the program.
personal git repositories of Harald Welte. Your mileage may vary