Age | Commit message (Collapse) | Author |
|
'goog/qcom/release/LA.UM.8.1.C9.09.00.00.518.167' into qt-r1-dev
Conflicts:
ipacm/src/Android.mk
Bug: 134087013
Change-Id: I945efee74f60a919916d4632a3e7c83512b61245
|
|
|
|
Bug: 128542475
Bug: 129245318
Change-Id: I96804ca004b4feb576294af9b4981624b68cf346
|
|
'goog/qcom/release/LA.UM.8.1.C9.09.00.00.518.158' into qt-r1-dev
Bug: 132954074
Change-Id: If77548c6d39e38c30b98d00abbf66810562ff72b
|
|
Use the correct name of vendor_product.mk and
put in the right path.
Change-Id: I7d3e004d8bb0f992e1171c7b2138c23926899108
|
|
|
|
'goog/qcom/release/LA.UM.8.1.C9.09.00.00.518.140' into qt-dev
Bug: 131711189
Change-Id: I281a4ad98420fee2011d443c68104b4dc34a833f
|
|
Add the support to offload the intra-bss traffic
between softap clients to use IPA-HW.
Change-Id: I86bee6a5777375008ff54113cb1457333b7253ca
|
|
Seeing ipacm was using the wrong mux-id
to construct modem UL clat rules which
causes modem drops those non-translated
ipv4 pkts. The fix is to propagate the
right mux-id to LAN/WLAN instance to
install the modem UL clat rules with
right clat mux-id.
Change-Id: Ie1e363866489fe67782b6b3abf41ff6fb2e75b22
|
|
Put WIGIG_CLIENT_CONNECT event inside flag to fix compilation issue.
Change-Id: Ib4bd2bb024890485e9ea1fee20ad9c26e4cf0991
|
|
|
|
|
|
|
|
data.lnx.5.1
|
|
11AD protocol is operated by WIGIG driver and is connected to IPA by
ipa_wigig client. This change adds data path changes to offload 11ad
clients.
Change-Id: I288f9587ab86d5ac52c66024982a80beeeeeb6b1
|
|
Add atoll to IPA v3 target list.
Change-Id: I28bd9d49772c9c5d1048eeef7a11f7a87bfb18bc
|
|
Add lito in v3 target list.
Change-Id: Ibd92729955f2b1050598c4e01aaafaca075c1b25
|
|
FR 53051 dictates tech teams to move module definitions
from common board package makefiles into individual
product make file specific to each module. As part of
this requirement we have made the following changes:
* Move opensource data ipcam module definitions from
base.mk into a new file called
ipacm_prop_vendor_product.mk
* Created new .rc files for ipacm and moved the
configurations from init.qcom.rc into ipacm.rc
Change-Id: I287125ac6d8d876a32abb453de2158252abcfb75
|
|
There is a race condition between setupstream and IPA_NEW_NEIGH_EVENT.
If we receive IPA_NEW_NEIGH_EVENT after setupstream, IPA_HANDLE_WAN_UP_TETHER
event is not posted. Post IPA_HANDLE_WAN_UP_TETHER event inside
handle_route_add_evt method to avoid the race condition.
Change-Id: I5d884075e463749325d6ee2d6541c4aea4859183
|
|
After SSR if we receive different number of rules than bootup,
still same number of rule is getting installed as bootup.
Reset ext prop flag ext_prop variable after SSR to install
correct number of rules.
Change-Id: Ie00ca5c70a2929b3840a11965a877f79055d7d3a
|
|
'goog/qcom/release/LA.UM.8.1.C9.09.00.00.518.121' into qt-dev
Bug: 130581568
Change-Id: I4c99f34745058a50f9e141dc5d1587617b199c37
|
|
Bug: 129559122
Change-Id: I22fd3d8adbf784e67848aed66e40842bfb67f2b3
|
|
am: a72ec4bb63
Change-Id: I3dcd95ac554bc328a17610232554e3718434cfa2
|
|
Change-Id: I52808b6fa2745139f2b636a34a109cd72ab2d1ae
BUG: 129345239
|
|
Use the same definition of NAT filter rule miss.
As defined at the kernel instead of the local one.
Change-Id: Ibab08a056518a661e4aec87ed352f319b127f30b
|
|
* changes:
Merge remote-tracking branch 'goog/qcom/release/LA.UM.8.1.C9.09.00.00.518.090'
Merge remote-tracking branch 'goog/qcom/release/LA.UM.8.1.C9.09.00.00.518.081'
|
|
Change-Id: I55dd8aaacde8cdcf95fa51c2845407f54bd64d2a
|
|
Bug: 128639903
Change-Id: I07a47e0744a24448d251f6e4fff2549b047c04c6
|
|
Bug: 127924739
Change-Id: If569ffb06a5031d1b9e07a0064a5cf06ca83fee6
|
|
|
|
On modem xlat scenario, due to the metadata replacement
after NAT, the vdev-ID is not retainned after the first
pass in ipa-hw, resuled in 2st-pass pkts sometimes go
to AP exception pipe and dropped. The fix is to disable
metadata replacement for XLAT ipv4 flt rules.
Change-Id: Iad0b589d3a938460770d4cfe87f45604639d19cf
|
|
Removed debug tag for IPACM module from LOCAL_MODULE_TAGS since
it is deprecated. It conflicted with the ability for products
to specify which modules should be installed.
Change-Id: I84b7995644670cf2db86e14dff55458d645da820
|
|
Bug: 124450013
Change-Id: I852c6bbbca0c874f0f0def96280904e42c99daf5
|
|
Bug: 123862805
Change-Id: I4f379ead23217d113e6de68c5c309916bc464a08
|
|
SM6125 target is not added in V3 target list, so correct QMI msg
is not being sent to Q6. Add SM6125 to IPA v3 target list.
Change-Id: I3b80bdc56708919f716a81e4967fdaa58b38754d
|
|
Add kona target to IPAv3 target list as kona
uses IPAv3 driver.
Change-Id: I75091e46d90e3489372a122a15f92649ed5404e8
|
|
Bug: 123059966
Change-Id: Ie47fa65648488255d14a381557d4ea73fdc52c03
|
|
Bug: 122718553
Change-Id: Icfbe3a153b11741be4855cf8c45fd013ea912762
|
|
When XLAT is enabled, mux_id will not be configured. Make
changes to use xlat_mux_id to configure the metadata in PDN
table.
Change-Id: Ic1646bbc4ff66e3f4911098041d2dfaf0670950d
|
|
Insert fallthrough statement to fix compilation
error for unannotated fall-through between switch
labels.
Change-Id: Ibc5f3f0cdc29e8144a47059c31ce15441a90ddac
|
|
Change-Id: I0c75d813d2e2d9d840c983e2ef2559b0558a236b
|
|
It will be a global error by default.
Test: make checkbuild
Bug: 112564944
Change-Id: Iae843ff17e0fcd5b84514d76dd6840106446305f
Exempt-From-Owner-Approval: do not block on new warnings
|
|
If the underlying HAL service object is invalidated, it
might result in a HAL transaction failure and the ipacm
process would be forced to abort.
To prevent the transaction error, use the isOk check right
after the HAL API is invoked to check whether the HAL
transaction was successful or not.
Change-Id: I4d71b35b6a31a6b705c1f61b542e1e82d1716a21
CRs-Fixed: 2340020
|
|
If the underlying HAL service object is invalidated and we did not get
a chance to invalidate it internally we may hit HAL transaction failure
error and the process would be forced to abort. To prevent the
transaction error we need to use the isOk check right after the HAL API
is invoked to check whether the HAL transaction was successful.
Change-Id: Idd21209f5c0407b75c2637190df5ba8158ef1a80
|
|
Fix the ipv6 frag pkts going to sw-exception
issue. Update the TCP ipv6 fragment rule attribute
on LTE use-case.
Change-Id: I53dcdf624cbc29146a7e095e7cc043584e919795
|
|
'goog/qcom/release/LA.UM.7.1.R1.09.00.00.461.057' into pi-dev am: 5c6ae3735a
am: 0536561738
Change-Id: Ifdf5e4235397aaa1e59c72445c37d3e627437432
|
|
'goog/qcom/release/LA.UM.7.1.R1.09.00.00.461.057' into pi-dev
am: 5c6ae3735a
Change-Id: Ie4fdc4bee60fbddec4d3bec5273e8594212718a9
|
|
'goog/qcom/release/LA.UM.7.1.R1.09.00.00.461.057' into pi-dev
Conflicts:
ipacm/src/Android.mk
Bug: 117197316
Change-Id: Ib75e02188e4bfc221ae7517b75182c4aa38c96d9
|
|
am: e1e3413c93
Change-Id: If14ac948ead5b8b6a859b7ee82c27582300cfa10
|
|
am: ac96cd8c8a
Change-Id: Icbabdd7ec24abfc7a131866bff61c90a524ec705
|