Remove nfc_initiator_transceive_dep_bytes() and introduce NDO_EASY_FRAMING option.
Always use nfc_initiator_transceive_bytes(). If you where using advanced features and already relying on nfc_initiator_transceive_bytes(), then your code has to be updated to unset the NDO_EASY_FRAMING option. See an example of such a change in the libfreefare's repository: http://code.google.com/p/nfc-tools/source/detail?r=566 Updates issue 106 Status: Feedback Romuald: I am not sure about the option enum values. I took 0x02 thinking it would not hurt but am not really sure about that because I can see many 'holes' in the sequence.
This commit is contained in:
parent
b1f4c38f8f
commit
a5676ecd94
9 changed files with 34 additions and 57 deletions
|
|
@ -66,8 +66,8 @@ bool nfc_initiator_mifare_cmd(nfc_device_t* pnd, const mifare_cmd mc, const uint
|
|||
if (szParamLen) memcpy(abtCmd+2,(byte_t*)pmp,szParamLen);
|
||||
|
||||
// Fire the mifare command
|
||||
if (!nfc_initiator_transceive_dep_bytes(pnd,abtCmd,2+szParamLen,abtRx,&szRxLen)) {
|
||||
nfc_perror (pnd, "nfc_initiator_transceive_dep_bytes");
|
||||
if (!nfc_initiator_transceive_bytes(pnd,abtCmd,2+szParamLen,abtRx,&szRxLen)) {
|
||||
nfc_perror (pnd, "nfc_initiator_transceive_bytes");
|
||||
return false;
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue