History log of /external/libnfc-nxp/inc/phNfcLlcpTypes.h
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
4bbf618b661ce7787efab168dd106115268fd539 27-Jan-2012 Sunil Jogi <sunil.jogi@nxp.com> Increase internal LLCP buffers to fit max MIU

Interal buffer increased to 2178 = 3 (max LLCP header size)
+ 128 (default MIU)
+ 2047 (max MIU)

Change-Id: I3cc2ff705e74ae657d93b5e50a577b0e7e5ebfcf
/external/libnfc-nxp/inc/phNfcLlcpTypes.h
7b187e70a5f0ffc021cc06a9f1a2bf2c0f8f8767 16-Jan-2012 Sunil Jogi <sunil.jogi@nxp.com> LLCP 1.1 implementation.

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
/external/libnfc-nxp/inc/phNfcLlcpTypes.h
3002430f96eb9c9f37806404e7dcfc944da383af 25-Jul-2011 Martijn Coenen <maco@google.com> Increase number of LLCP sockets from 5 to 10.

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
/external/libnfc-nxp/inc/phNfcLlcpTypes.h
5d9927ba30ba449badb9f6df0fbeb4d6aedc6e2a 23-Sep-2010 Nick Pelly <npelly@google.com> Initial libnfc checkin

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>
/external/libnfc-nxp/inc/phNfcLlcpTypes.h