search

Roverok / libnfc

Automatically exported from code.google.com/p/libnfc
GNU Lesser General Public License v3.0
0 stars 0 forks source link

Catch unsupported command before sending to chip #92

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This issue was created by revision r484.

Actually, libnfc support PN531, PN532 and PN533 NFC chips, but the devices does 
not the same features. e.g. PN531 does not support ISO14443B modulation.
It should great to catch theses unsuported commands before sending to chip in 
order to prevent a chip error.

Original issue reported on code.google.com by romu...@libnfc.org on 30 Jul 2010 at 11:46

GoogleCodeExporter commented 9 years ago 
AFAIK, we can add: PN531 does not support hardware polling

Original comment by romu...@libnfc.org on 16 Aug 2010 at 3:56

GoogleCodeExporter commented 9 years ago 
Romain, could you easily introduce these unsupported command errors in your new 
error-handling branch ?

Original comment by romu...@libnfc.org on 16 Aug 2010 at 3:59

GoogleCodeExporter commented 9 years ago 
Hum.  Catching some device-specific returned error code and generalizing them 
is just the missing piece in the puzzle.  This looks like a great idea!

I'll take it

Original comment by romain.t...@gmail.com on 16 Aug 2010 at 7:05

GoogleCodeExporter commented 9 years ago 
Fixed in r560.

Original comment by romain.t...@gmail.com on 20 Aug 2010 at 10:20