diff options
| author | Pavel Kubelun <be.dissent@gmail.com> | 2017-12-02 02:26:11 +0300 |
|---|---|---|
| committer | Felix Fietkau <nbd@nbd.name> | 2018-01-17 11:02:05 +0100 |
| commit | 36a96a449303560395e9566faee58afbfdab745d (patch) | |
| tree | 8a4da6d42f07b68e70d5f50579402df35bfad113 /target/linux/ipq806x/Makefile | |
| parent | 3c4df661c0c8d693b5198cbbf61f679c76fdea52 (diff) | |
| download | upstream-36a96a449303560395e9566faee58afbfdab745d.tar.gz upstream-36a96a449303560395e9566faee58afbfdab745d.tar.bz2 upstream-36a96a449303560395e9566faee58afbfdab745d.zip | |
ipq806x: fix wireless regression
In current state there's huge regression on ipq806x target that causes the device to transmit broken/malformed frames that are not corrected/detected by error control mechanisms and other less severe issues.
https://bugs.lede-project.org/index.php?do=details&task_id=1197
This finally had been narrowed down to patch 0071-pcie-qcom-fixes.patch
Meanwhile QSDK contains a handful of commits that add support for ipq806x to upstream qcom pcie driver
https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/log/drivers/pci/host/pcie-qcom.c?h=eggplant
Unfortunately qca developers do not bother to push it upstream.
Using those commits instead of lede 0071 patch fixes mentioned issue and probably many others as it seems that corrupted data has been originating within pcie misconfiguration.
Fixes: FS#1197 and probably others
Signed-off-by: Pavel Kubelun <be.dissent@gmail.com>
Diffstat (limited to 'target/linux/ipq806x/Makefile')
0 files changed, 0 insertions, 0 deletions