FW can dynamically adjust to multiple mac
addresses. It reports it's preferred base mac
address, but we can freely create derivative
addresses for vdevs.

Signed-off-by: Michal Kazior <michal.kaz...@tieto.com>
---
 drivers/net/wireless/ath/ath10k/wmi.c |    8 --------
 1 file changed, 8 deletions(-)

diff --git a/drivers/net/wireless/ath/ath10k/wmi.c 
b/drivers/net/wireless/ath/ath10k/wmi.c
index 0d5070d..895567b 100644
--- a/drivers/net/wireless/ath/ath10k/wmi.c
+++ b/drivers/net/wireless/ath/ath10k/wmi.c
@@ -907,14 +907,6 @@ static int ath10k_wmi_ready_event_rx(struct ath10k *ar, 
struct sk_buff *skb)
 
        memcpy(ar->mac_addr, ev->mac_addr.addr, ETH_ALEN);
 
-       /* FIXME: FW should report possible addresses we can use. This is a
-        *        development workaround. wpa_supplicant generates addresses
-        *        that do not work with the FW without this. Once this is
-        *        submitted upstream we should either get rid of this either by
-        *        reducing functionality or forcing FW team to take action. */
-       memcpy(ar->hw->wiphy->perm_addr, ev->mac_addr.addr, ETH_ALEN);
-       memcpy(ar->hw->wiphy->addr_mask, "\x00\x00\x00\xFF\xFF\xFF", ETH_ALEN);
-
        ath10k_dbg(ATH10K_DBG_WMI,
                   "wmi event ready sw_version %u abi_version %u mac_addr %pM 
status %d\n",
                   __le32_to_cpu(ev->sw_version),
-- 
1.7.9.5

_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to