| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ic6df1fc458cef2531119e5e5e2ef5f9a7b21a524
|
|
|
|
|
|
|
|
| |
Interal buffer increased to 2178 = 3 (max LLCP header size)
+ 128 (default MIU)
+ 2047 (max MIU)
Change-Id: I3cc2ff705e74ae657d93b5e50a577b0e7e5ebfcf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, in LLCP v1.0, the only way to use the SDP (Service
Discovery Protocol) service was to send a CONNECT frame containing
the Service Name to the SDP service. This was implicitly
preforming a connection request to the requested service.
LLCP v1.1 introduced a way to discover services more efficiently
and without implicit connection. It also enables connectionless
services to have a service name. It is based on a new protocol
based on a new SNL frame containing discovery requests and
responses.
This update comes with new APIs:
- phLibNfc_Llcp_DiscoverServices() function can be used to discover
remote services. It can take multiple service names and resolve
all of them in a single call.
- Register service name at bind time. Cache LLCP service name/sap pairs.
In LLCP 1.1 specification defines at section 5.9 that any service
lookup answer must be valid for the whole LLCP session duration.
To enforce this, we cache the SAP/SN pairs locally and make sure
that the applications don't break the cache.
The stack remains fully retro-compatible with v1.0 devices.
Change-Id: I052edd3838013cee65e7415d0ed01fc3e9cad36d
|
|
|
|
|
|
|
|
|
|
| |
The NFC HAL in libhardware allows us to store and retrieve
product-specific settings. This patch moves two product-specific
settings to the HAL: the device port, and the usage of the i2c
workaround we had for crespo. This means configuring the port
no longer needs to be done from JNI land.
Change-Id: I2e19b6f188f808bc2f2a1f1abc28f2a6c47e6a4c
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This provides a path to flush RX, necessary when we enter FW download mode
with bogus data already in RX. This fixes a problem where NFC was dead on several
HSPA and LTE devices.
Also decrease FW timeout completition from 120s to 60s. Typically FW download
takes 30s, and 120 is unnecessarily large and causes a long delay to bring up
NFC when we need to retry FW.
Bug: 5468674
Change-Id: I0fd40c199daac861fe5acda4f2d214bdcff8e869
|
|
|
|
|
|
|
|
|
|
| |
Patch to add Secure Download Mechanism in the libnfc
This patch permit to support secure download update and
also to avoid locking states in case of download failures
Bug: 5331837
Change-Id: Ia5b6d9baf57231b0193bbbe85c88c7df557017c6
|
|
|
|
|
|
|
|
|
|
|
| |
We currently have 3 server sockets open (snep, npp, bluetooth); I found
that when we traverse from snep to npp (as a fallback), then do
bluetooth, we run out of sockets (NFCSTATUS_INSUFFICIENT_RESOURCES
is returned on socket creation). This is because cleanup of the sockets
is asynchronous and the previous 2 sockets may still be disconnecting.
Increasing to 10 should be enough for ICS purposes.
Change-Id: I803da4cbcc97e7c5b736bf7276d2bbb7136c6dc3
|
|\
| |
| |
| |
| |
| |
| | |
firmware events
* commit '51c0ca53011b86464dcf14aeb33944a69861a8f4':
Patch to support the new PN544 firmware events
|
| |
| |
| |
| | |
Change-Id: I6e5a976721fb52f2da30081276bb2ac15d27d186
|
| |
| |
| |
| |
| |
| |
| |
| | |
This patch enables windowing of LLC packets send from chipset to host.
The host will now wait for up to 4 LLC packets from the chipset before
sending an ACK (S-Frame RR).
Change-Id: I6a70e1d780847a104e3ec8e403593a69e222aec9
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
o Fix most libnfc warnings, from 360 to 18
o Make DAL_DEBUG much less verbose and more useful
o Clean up Android.mk
Done with minimal textual diff to minimize merge conflicts.
Change-Id: I918645500723ff7bb092ad9959628fcabac45bec
|
|/
|
|
|
|
|
|
|
| |
Adds an interface for setting the NfcA timeout, which
is called "mifare raw" in libnfc. Also changed the default,
since it was set to only 2 ms, which is too short for most
commands. Current setting is around 600ms.
Change-Id: I00ccd85cd47a70895a3aca0f0bc34e1b0eab82c7
|
|
|
|
|
|
|
|
| |
o Fix DEFAULT_NFCIP_INITIATOR_MODE_SUPPORT, DEFAULT_NFCIP_TARGET_MODE_SUPPORT
to allow all possible modes (actual modes selected by Nfc.apk).
o Fix phNfc_eP2PMode_t enum to list initiator modes.
Change-Id: I841b6f1387ac536f47d357a0430eb9362b419810
|
|
|
|
|
|
| |
Disabling P2P 106 passive caused a large P2P discovery regression.
Change-Id: I9856ba1a29cd717da2f578abd073b341c54fce36
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
P2P target 106 passive appears as an ISO 14443-3A target to reader/writers
in the field. This can confuse some terminals, especially when we also have
card emulation turned on, since it looks like we have two -3A targets in
the field.
P2P target 106 passive is just one of many P2P sub-modes. We do not know of any
P2P devices that only initiate using only 106 passive, so this should not
present inter-op issues.
Change-Id: I1cb84ed791a86a7f225a51806e99bab031dcb6ca
|
|
|
|
| |
Change-Id: I6f3a96b9b063b66f735ff97c1aa63aaaad0a03b9
|
|
|
|
| |
Change-Id: Idcbf0ab9b982b66c39b68762129766e16017558c
|
|
|
|
| |
Change-Id: Id2991644e9a45a66172377d66b5dc3e99bbd6a39
|
|
|
|
|
|
|
| |
This is needed for proper multi-protocol tag support.
(Before this required a restart of the polling loop).
Change-Id: If61da437cda40d82bdbacf5a01ea4c585c7a5be9
|
|
|
|
| |
Change-Id: Idfed8c90453a0acc7fa632f62a1e20617b4ae7f6
|
|
|
|
| |
Change-Id: Ica5158d1851fe56a896b6a0d8d714d8aa9d6b029
|
|
|
|
| |
Change-Id: I150411fb826525ae30cbe36e2be9afb1f20deb19
|
|
|
|
| |
Change-Id: I2bef50244d216d76f3f81df20e4f0b2cddea3d86
|
|
|
|
| |
Change-Id: I5a34e5318d60d04cbb4f43bcba7a146c2ef9eed5
|
|
|
|
|
|
|
|
|
| |
This is effectively a revert of previous commit "Fix to disable P2P...", except
I have not reverted the DEFAULT_SESSION since that would encourage reuse of
'goog4'.
Change-Id: I8d42a7496cf6776cfd41e73f5ec25953773ceb09
Signed-off-by: Nick Pelly <npelly@google.com>
|
|
|
|
|
| |
Change-Id: I6bbabdd141962dd60ff7fadc39fc047be15b055e
Signed-off-by: Nick Pelly <npelly@google.com>
|
|
|
|
|
| |
Change-Id: Iee39957227fcdc8e97b520d22032dc97915323f3
Signed-off-by: Nick Pelly <npelly@google.com>
|
|
|
|
| |
Change-Id: Ic27ec9adbdffb064f03f567b160b05502def2444
|
|
|
|
|
|
| |
This reverts commit 4c03147f9df22103145e67ce1d7faece051e0bfb.
Change-Id: I44496a47a98367b88ae69d019d363bd0fa962611
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NFC_IP mode controls the P2P modes that the PN544 operates in. This change
turns off 106kb/s passive (P2P target mode).
The reason for this change is that enabling P2P target at 106 kb/s can
interfere with card emulation. Some 106kb/s card readers will enumerate
the pn544 as two distinct targets if we have 106kb/s card emulation and
106kb/s P2P target, and they will then refuse to talk to us. So this is
basically for legacy support of 106kb/s card emulation.
NXP advise that it is a common change to disable 106kb/s P2P target. We still
enable 212kb/s and 424kb/s P2P target.
Secondly, we need to choose a different session ID to force the pn544 to
apply this new configuration (instead of just loading the previous from
EEPROM).
Change-Id: I2847c04bb028b857223439dc1f9f6252162913c4
Signed-off-by: Nick Pelly <npelly@google.com>
|
|
|
|
|
| |
Change-Id: Ib6563a94b29c7eb9de6615881eadbdf0e94994c8
S5PC11X: NFC: Enable the STANDBY mode and add enableDiscovery and disableDiscovery for polling loop.
|
|
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>
|