ACR122 readers are not found with nfc_connect()

[GoogleCodeExporter]

While ACR122 driver is back in trunk, that have been reported that trunk (r940) 
doesn't work without tag on top of device (on "true" ACR122, not touchatag).

But, currently we don't have the device to test, so I put an issue to don't 
forget to fix it before releasing.

Original issue reported on code.google.com by romu...@libnfc.org on 8 Mar 2011 at 3:14

[GoogleCodeExporter]

Sorry that was my way of testing which was wrong, using a mix of nfc-list & 
pn53x-tamashell.

The good news is:
- ACR122 works with or without tags on it

The bad news is:
- only nfc-list finds the ACR122 and the Touchatag
other commands using a simple nfc_connect(NULL) fail finding those readers

$ ./nfc-anticol
Error connecting NFC reader
$ ./nfc-list
Connected to NFC device: ACS ACR 38U-CCID 00 00 / ACR122U102
Connected to NFC device: ACS ACR122U PICC Interface 02 00 / ACR122U203 - PN532 
v1.4 (0x07)

Original comment by yob...@gmail.com on 8 Mar 2011 at 7:15

• Changed title: ACR122 readers are not found with nfc_connect()

[GoogleCodeExporter]

Works for me: here, with one Touchatag (ACS ACR 38U-CCID 01 00 / ACR122U102) 
plugged, it works using nfc-anticol.
BTW, there is something strange in your lines:
Connected to NFC device: ACS ACR 38U-CCID 00 00 / ACR122U102
Connected to NFC device: ACS ACR122U PICC Interface 02 00 / ACR122U203 - PN532 
v1.4 (0x07)

The first device haven't reported correctly his PN53x firmware version.
I need a similar setup I think to reproduce your bug.

Original comment by romu...@libnfc.org on 9 Mar 2011 at 11:55

• Changed state: Feedback

[GoogleCodeExporter]

This issue was closed by revision r947.

Original comment by rtarti...@il4p.fr on 9 Mar 2011 at 1:49

• Changed state: Fixed