There is a patch added here to ath10k to bypass some checks on startup.  I 
believe this is related to the calibration data being provided in external 
files (dumped from the ART mtd partition at init time) rather than directly 
from the pcie board.  The patch and related discussion is from here: 
http://lists.infradead.org/pipermail/ath10k/2015-November/006489.html.  But am 
following up further on the ath10k list, since it may also be related to the 
board bin files in ath10k-firmware.  (follow-up thread here: 
http://lists.infradead.org/pipermail/ath10k/2015-December/006613.html)


Signed-off-by: Josh Bendavid <joshbenda...@gmail.com>


---
 .../mac80211/patches/941-ath10k_skip_otp_check.patch      | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
 create mode 100644 
package/kernel/mac80211/patches/941-ath10k_skip_otp_check.patch

diff --git a/package/kernel/mac80211/patches/941-ath10k_skip_otp_check.patch 
b/package/kernel/mac80211/patches/941-ath10k_skip_otp_check.patch
new file mode 100644
index 0000000..09cf82c
--- /dev/null
+++ b/package/kernel/mac80211/patches/941-ath10k_skip_otp_check.patch
@@ -0,0 +1,15 @@
+diff -ur 
../../old/compat-wireless-2015-12-03/drivers/net/wireless/ath/ath10k/core.c 
./drivers/net/wireless/ath/ath10k/core.c
+--- a/drivers/net/wireless/ath/ath10k/core.c   2015-12-06 23:36:07.696995166 
+0100
++++ b/drivers/net/wireless/ath/ath10k/core.c   2015-12-07 00:01:50.390388435 
+0100
+@@ -1800,9 +1800,9 @@
+ 
+       ret = ath10k_core_get_board_id_from_otp(ar);
+       if (ret && ret != -EOPNOTSUPP) {
+-              ath10k_err(ar, "failed to get board id from otp: %d\n",
++              ath10k_err(ar, "failed to get board id from otp: %d, 
ignoring\n",
+                          ret);
+-              return ret;
++//            return ret;
+       }
+ 
+       ret = ath10k_core_fetch_board_file(ar);
-- 
2.6.4
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to