| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
LLCP state was not reset properly.
Bug: 5971895
Change-Id: I4fda6ef7c78ae2730359cf5c90d887d205e57799
|
| |
|
|
|
|
|
|
|
| |
Some parts of the code reset the state to an operation state,
even if the link has already been shutdown. This allowed for a second
deactivation callback, causing a crash higher up in the stack.
Bug: 5765077
Change-Id: I2f2ac720756353d45d82634d27a3dd9acecae43d
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The LLCP stack was holding onto the "I'm allowed to send" token
for the full link time-out, even if there was nothing to send. This
caused very bad round-trip delays. This fix just gives the token
back immediately if there's nothing to send.
Change-Id: Ib7bf87bd5fada2b682d28c9502b5ef010cd39815
|
| |/
|
|
| |
Change-Id: I94f16770d1803f89370df5a798a6c76670581a63
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Send failures on LLCP sockets were not dealt with at all - the transport
was just left in a state where it thought there was a pending send
and a pending callback. Before we typically only did one send and
it didn't bite us so much, but now with multiple sockets we run
into this frequently.
This really just fixes part of the problem - we should also look
if state rollbacks are necessary, as those are not done either
on send failures.
Change-Id: I484ca598e043ead835251aedaabe47d3a1da7a8f
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
The LLCP specification defines that if a TLV cannot be interpreted,
it shall be ignored rather than generating an error.
This patch removed all error reporting on TLV interpretation. The
only error that can still happen is length inconsistency in the
whole TLV array buffer.
Change-Id: Ibf289fceb2283bfddcdc0ddee9e687ece3e90887
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The parsing algorithm for AGF frames has been fixed. It was previously
only working if aggregated frames were 4-bytes long.
The current stack only support mandatory de-aggregation. It does not
send aggregated frames, so there won't be interop issue with previous
versions.
This fix prevents reading erroneous de-aggregated frames and rejecting
them using FRMR when communicating with an LLCP implementation
using aggregation mechanism.
Change-Id: Ia5728496a2917b6a57f478cc51dc0aaa0fcc165a
|
| |
|
|
| |
Change-Id: I08e8dda5ae23ec251a5b53f71b0e87fb3ba7d02c
|
| |
|
|
|
|
|
| |
Check that internal allocated buffer is not NULL before deallocating
it and make sure the pointer is resetted to NULL.
Change-Id: I4212489c8661c7a8dff8ef352029100ec5ab157e
|
| |
|
|
|
|
|
| |
This avoids an application to be stuck in a send request while the
LLCP link has been lost (i.e. remote peer lost).
Change-Id: I74982d497c410ae4bdb466afac013efc9eb17b03
|
| |
|
|
| |
Change-Id: I2a857c4e02fcf8c0f655a6fa960466f5ac4f191e
|
| |
|
|
|
|
| |
Makes sure to call callback in case of error and before deactivating.
Change-Id: I40cf77a89edc01533684c9c68b1915dac983c59e
|
| |
|
|
| |
Change-Id: I85a4235a4f13e02a61d2c07ca301e72e7b369c8b
|
| |
|
|
| |
Change-Id: I11e80e9778934e40e57c58dbc9f56f319d015f80
|
| |
|
|
|
|
| |
Use dynamic allocation and copy to avoid using invalid pointers.
Change-Id: I19ff26776fdc42fb4d3bf519a6e742d76b45ded1
|
|
|
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>
|
