sys-kernel/linux-{image,headers} : version bump

1 files changed, 35 insertions, 0 deletions

diff --git a/sys-kernel/linux-image/files/0001-Revert-ath10k-activate-user-space-firmware-loading-a.patch b/sys-kernel/linux-image/files/0001-Revert-ath10k-activate-user-space-firmware-loading-a.patch
new file mode 100644
index 00000000..281ede4b
--- /dev/null
+++ b/sys-kernel/linux-image/files/0001-Revert-ath10k-activate-user-space-firmware-loading-a.patch
@@ -0,0 +1,35 @@
+From 180dee4ae482fd31fb7f53f7e2d2bd62d1210383 Mon Sep 17 00:00:00 2001
+From: Gabriel Craciunescu <nix.or.die@gmail.com>
+Date: Mon, 13 Nov 2017 12:54:26 +0100
+Subject: [PATCH] Revert "ath10k: activate user space firmware loading again"
+ This reverts commit c0cc00f250e19c717fc9cdbdb7f55aaa569c7498.
+
+  Huh ? That fixes nothing but introduce *again* flooding users
+  dmesg with 'strange' firmware loading failures.
+  As example a hw1.0 QCA9377 card floods with:
+
+  ...
+  ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:03:00.0.bin failed with error -2
+  ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/cal-pci-0000:03:00.0.bin failed with error -2
+  ath10k_pci 0000:03:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-6.bin failed with error -2
+  ...
+---
+ drivers/net/wireless/ath/ath10k/core.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/drivers/net/wireless/ath/ath10k/core.c b/drivers/net/wireless/ath/ath10k/core.c
+index a4f635820f35..9b4c4facf725 100644
+--- a/drivers/net/wireless/ath/ath10k/core.c
++++ b/drivers/net/wireless/ath/ath10k/core.c
+@@ -519,7 +519,7 @@ static const struct firmware *ath10k_fetch_fw_file(struct ath10k *ar,
+ 		dir = ".";
+ 
+ 	snprintf(filename, sizeof(filename), "%s/%s", dir, file);
+-	ret = request_firmware(&fw, filename, ar->dev);
++	ret = request_firmware_direct(&fw, filename, ar->dev);
+ 	ath10k_dbg(ar, ATH10K_DBG_BOOT, "boot fw request '%s': %d\n",
+ 		   filename, ret);
+ 
+-- 
+2.15.0
+