| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|
|
|
|
| |
Change-Id: I8da74ff64579181387b3905c29e5d4dca9e9e7eb
Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
|
|
|
|
| |
Change-Id: If3afc9a3d46fe3780261d029caac18d242718e38
|
|
|
|
|
|
| |
* So we stay bug-for-bug compatible with OEMs.
Change-Id: I0c14568d9f587ebcd2d21c0f0490b705be7ce8ce
|
|
|
|
|
|
|
|
|
| |
https://android.googlesource.com/platform/packages/apps/Nfc into HEAD
Conflicts:
nxp/jni/com_android_nfc_NativeNfcManager.cpp
Change-Id: Ic84af6ad1cda79984f40e9fc464d2cbaa994b89a
|
|
|
|
|
| |
Bug: 7276355
Change-Id: If2732afd542a68dc440308dae9eb76eb7ff31e25
|
|
|
|
|
|
| |
This was regression from a JB change.
Change-Id: Idbd92abf797478ec827dc26d6e825e2a6805356d
|
|
|
|
|
|
|
| |
The new NCI stack can deal with larger MIU and
rw sizes, which give us better p2p throughput.
Change-Id: I6600f28ddafe142b64ead2df896823bb8d242fc5
|
|\
| |
| |
| |
| | |
* commit 'bb65a8d87ee523c92ca1b5f57efe139bab3859fe':
Allow NfcB connects in NCI stack.
|
| |
| |
| |
| |
| |
| |
| | |
PN544 did not support this - move the code checking for that
into dh implementation.
Change-Id: I4def57697bc81cf599421f1ffbfa85c0db72c458
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From partner drop at 07/20. Modified to fit into our new
JNI/DH split.
New build config that builds two targets,
Nfc and NfcNci, each with their own dependencies. Product config files
have to specify either Nfc or NfcNci in their packages config.
Change-Id: I348a3aad7167195ca03baf9636408ab8e4c55fce
|
| |
| |
| |
| |
| |
| |
| | |
The DeviceHost classed moved to a new package,
updated the JNI references accordingly.
Change-Id: I11d30b241f80e2efba4570a921346ea3689b4ec5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Preparation for the new NCI stack. The idea is to
build either the NXP or the NCI stack, triggered
by a makefile switch. To that end, move the
DeviceHost and JNI implementations in their own
directory, so we can build them only if needed.
Change-Id: I8579ec30ceb1908e4cd180cfbd10224aa4bddb8d
|
| |
| |
| |
| |
| |
| |
| |
| | |
NOT MERGE)
This reverts commit 26f6049196acaa9768ba6bdef343216ea878a4c1.
Change-Id: I7ed3a1ba24bbbdb3336547c20f47c344d70b2d30
|
|
|
|
|
|
|
|
|
|
| |
Preparation for the new NCI stack. The idea is to
build either the NXP or the NCI stack, triggered
by a makefile switch. To that end, move the
DeviceHost and JNI implementations in their own
directory, so we can build them only if needed.
Change-Id: Ibb6aeb11f0bb887e153fd457860b1ad0e39e7933
|
|
|
|
|
|
|
|
|
|
| |
From partner drop at 07/20. Modified to fit into our new
JNI/DH split.
New build config that builds two targets,
Nfc and NfcNci, each with their own dependencies. Product config files
have to specify either Nfc or NfcNci in their packages config.
Change-Id: I348a3aad7167195ca03baf9636408ab8e4c55fce
|
|
|
|
|
|
|
| |
The DeviceHost classed moved to a new package,
updated the JNI references accordingly.
Change-Id: I11d30b241f80e2efba4570a921346ea3689b4ec5
|
|
|
|
|
|
|
|
|
|
| |
Preparation for the new NCI stack. The idea is to
build either the NXP or the NCI stack, triggered
by a makefile switch. To that end, move the
DeviceHost and JNI implementations in their own
directory, so we can build them only if needed.
Change-Id: I8579ec30ceb1908e4cd180cfbd10224aa4bddb8d
|
|
|
|
| |
This reverts commit 26f6049196acaa9768ba6bdef343216ea878a4c1.
|
|
Preparation for the new NCI stack. The idea is to
build either the NXP or the NCI stack, triggered
by a makefile switch. To that end, move the
DeviceHost and JNI implementations in their own
directory, so we can build them only if needed.
Change-Id: Ibb6aeb11f0bb887e153fd457860b1ad0e39e7933
|