Michal Kazior <[email protected]> writes:
> The 3.2 revision has a different target BMI
> version so it wasn't recognized by ath10k (despite
> the chip_id rev being on the supported list
> already).
>
> Signed-off-by: Michal Kazior <[email protected]>
But uses the same binaries as hw3.0?
> + {
> + .id = QCA6174_HW_3_2_VERSION,
> + .name = "qca6174 hw3.2",
> + .patch_load_addr = QCA6174_HW_3_0_PATCH_LOAD_ADDR,
> + .uart_pin = 6,
> + .fw = {
> + .dir = QCA6174_HW_3_0_FW_DIR,
> + .fw = QCA6174_HW_3_0_FW_FILE,
> + .otp = QCA6174_HW_3_0_OTP_FILE,
> + .board = QCA6174_HW_3_0_BOARD_DATA_FILE,
> + .board_size = QCA6174_BOARD_DATA_SZ,
> + .board_ext_size = QCA6174_BOARD_EXT_DATA_SZ,
> + },
> + },
> };
I added this in pending branch to avoid people wondering why it uses 3.0
binaries:
diff --git a/drivers/net/wireless/ath/ath10k/core.c
b/drivers/net/wireless/ath/ath10k/core.c
index 36a8fcf349fa..310e12bc078a 100644
--- a/drivers/net/wireless/ath/ath10k/core.c
+++ b/drivers/net/wireless/ath/ath10k/core.c
@@ -91,6 +91,7 @@ static const struct ath10k_hw_params ath10k_hw_params_list[]
= {
.patch_load_addr = QCA6174_HW_3_0_PATCH_LOAD_ADDR,
.uart_pin = 6,
.fw = {
+ /* uses same binaries as hw3.0 */
.dir = QCA6174_HW_3_0_FW_DIR,
.fw = QCA6174_HW_3_0_FW_FILE,
.otp = QCA6174_HW_3_0_OTP_FILE,
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
