external_libnfc-nxp.git - external/libnfc-nxp

	Commit message (Collapse)	Author	Age	Files	Lines
*	card emulation patch port to JB	doug yeager	2012-08-28	1	-323/+333
\| \| \| \|	Change-Id: I86657f9c547840de33c35df4912b5f282d4fe459
*	Patch to support MIFARE with SAK 0x01	Sunil Jogi	2012-04-02	1	-1/+2
\| \| \| \|	Change-Id: Ifb1389d428855c2eea99390790af13f28571097a
*	Fix for removing unnecessary DESELECT before P2P activation in case	Sunil Jogi	2011-08-24	1	-0/+4
\| \| \| \| \| \|	devices are moving in to the range and moving out of the range quickly Change-Id: I090367ad17de443c6af41c9ad507557e3eaaf7f9
*	Patch to support multiple connection on Multiple protocol TAG	Daniel Tomas	2011-07-14	1	-0/+8
\| \| \| \|	Change-Id: I0f09869458ebbc6d77363338975754335569b6a6
*	Narrow down NFCSTATUS_TARGET_LOST responses from libNFC.	Martijn Coenen	2011-02-18	1	-2/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	During extensive testing we found that some ISO15693 tags do not react to some commands. However, they do send an error code to the PN544 indicating they do not support the command. The PN544 in turn sends one specific error code over the HCI interface. However, libNFC maps that error code always to NFCSTATUS_TARGET_LOST, which in the end maps to the application API reporting a TargetLostException. This fix maps only the timeout return values from the PN544 to NFCSTATUS_TARGET_LOST; all other values are mapped to NFCSTATUS_FAILED, which in turn maps to an IOException at API level. In effect, a timeout is still not the same as a target lost; libNFC does not do any additional internal presence check to make sure the tag is really gone, although it usually is. I'll submit a separate fix on packages/apps/Nfc to take care of this. Change-Id: If64857658d683aff29134f74b42efd99b695e634
*	Add support for connecting to different handles on the same tag.	Martijn Coenen	2010-12-16	1	-0/+168
\| \| \| \| \| \| \|	This is needed for proper multi-protocol tag support. (Before this required a restart of the polling loop). Change-Id: If61da437cda40d82bdbacf5a01ea4c585c7a5be9
*	Fix failing presence check after a mifare classic reconnect.	Martijn Coenen	2010-12-13	1	-0/+1
\| \| \| \|	Change-Id: I6f833fc6e32cd99496468306af8204f6aee87fa7
*	LLCP modification for concurence accesses	daniel_Tomas	2010-12-05	1	-3/+12
\| \| \| \|	Change-Id: I428c58dfc2c791f87e0f5761f11bb59d26ad85b1
*	Secure Element access implementation	Daniel Tomas	2010-12-05	1	-0/+4
\| \| \| \|	Change-Id: I5a34e5318d60d04cbb4f43bcba7a146c2ef9eed5
*	Fix for presence check management after transceive failed	daniel_Tomas	2010-12-05	1	-0/+1
\| \| \| \|	Change-Id: I4ee3109710de339d105bd3e2721114b62d883275
*	Initial libnfc checkin	Nick Pelly	2010-09-23	1	-0/+1154
	Source: Trusted_NFC_Device_Host_AA03.01e02_google.zip code drop (23-Sep-2010) Change-Id: Ie47f18423f949a8d3e0815d13f55c814312add24 Signed-off-by: Nick Pelly <npelly@google.com>