nfctype2: Fix wrong read command length
authorEyal Reizer <eyalr@ti.com>
Mon, 18 Jun 2012 08:19:16 +0000 (11:19 +0300)
committerSamuel Ortiz <sameo@linux.intel.com>
Mon, 18 Jun 2012 13:58:27 +0000 (15:58 +0200)
commit80b075a6b6e2659dc2268873f9be69e1057a740b
treeb2ed57b2974a6572650d8cc7f56160adac986854
parent6e75063e781c47710fb99f14c1f1df7189c8a426
nfctype2: Fix wrong read command length

According to "Type 2 Tag Operation Specification" the read command is 2
bytes long: (Code=0x30 and Block number).

Instead of sending 2 bytes the code was sending 6 bytes which caused some
NFC controllers to send a wrong read command which resulted with a read
timeout.
plugins/nfctype2.c