diff options
author | Ben Greear <greearb@candelatech.com> | 2018-01-19 16:27:02 -0800 |
---|---|---|
committer | Jo-Philipp Wich <jo@mein.io> | 2018-03-22 09:09:54 +0100 |
commit | d0f3dd5b9f341763e79eb5baa77d2144ee5f4f98 (patch) | |
tree | 8d8f35d46bd2a3543cfafc6a51d0d6f3787ab35b /package/kernel/ath10k-ct/patches | |
parent | 3db9d6e57def2912314c7ce0bc0c282f313ed654 (diff) | |
download | upstream-d0f3dd5b9f341763e79eb5baa77d2144ee5f4f98.tar.gz upstream-d0f3dd5b9f341763e79eb5baa77d2144ee5f4f98.tar.bz2 upstream-d0f3dd5b9f341763e79eb5baa77d2144ee5f4f98.zip |
ath10k-ct: update to latest version, enable AHB.
The driver updates include:
ath10k driver backport to fix WPA 'pn' related security bugs
(4.13 based driver only currently),
a fix for off-channel TX for CT wave-1 firmware, a likely
fix for napi related crashes, and a backport of the firmware fetch
patch.
AHB is needed for the IPQ4019 platform radios.
Signed-off-by: Ben Greear <greearb@candelatech.com>
[use common subject format]
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Diffstat (limited to 'package/kernel/ath10k-ct/patches')
-rw-r--r-- | package/kernel/ath10k-ct/patches/130-ath10k-activate-user-space-firmware-loading-again.patch | 36 |
1 files changed, 0 insertions, 36 deletions
diff --git a/package/kernel/ath10k-ct/patches/130-ath10k-activate-user-space-firmware-loading-again.patch b/package/kernel/ath10k-ct/patches/130-ath10k-activate-user-space-firmware-loading-again.patch deleted file mode 100644 index dc02a9d6e9..0000000000 --- a/package/kernel/ath10k-ct/patches/130-ath10k-activate-user-space-firmware-loading-again.patch +++ /dev/null @@ -1,36 +0,0 @@ -From c0cc00f250e19c717fc9cdbdb7f55aaa569c7498 Mon Sep 17 00:00:00 2001 -From: Hauke Mehrtens <hauke@hauke-m.de> -Date: Thu, 24 Aug 2017 23:06:41 +0200 -Subject: [PATCH] ath10k: activate user space firmware loading again - -In commit 9f5bcfe93315 ("ath10k: silence firmware file probing -warnings") the firmware loading was changed from request_firmware() to -request_firmware_direct() to silence some warnings in case it fails. -request_firmware_direct() directly searches in the file system only and -does not send a hotplug event to user space in case it could not find -the firmware directly. -In LEDE we use a user space script to extract the calibration data from -the flash memory which gets triggered by the hotplug event. This way the -firmware gets extracted from some vendor specific partition when the -driver requests this firmware. This mechanism does not work any more -after this change. - -Fixes: 9f5bcfe93315 ("ath10k: silence firmware file probing warnings") -Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> -Cc: Michal Kazior <michal.kazior@tieto.com> -Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com> ---- - ath10k-4.13/core.c | 2 +- - 1 file changed, 1 insertion(+), 1 deletion(-) - ---- a/ath10k-4.13/core.c -+++ b/ath10k-4.13/core.c -@@ -556,7 +556,7 @@ static const struct firmware *ath10k_fet - dir = "."; - - snprintf(filename, sizeof(filename), "%s/%s", dir, file); -- ret = request_firmware_direct(&fw, filename, ar->dev); -+ ret = request_firmware(&fw, filename, ar->dev); - ath10k_dbg(ar, ATH10K_DBG_BOOT, "boot fw request '%s': %d\n", - filename, ret); - |