[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40854e84bd4b4a9699b60530b1c373ad@aptaiexm02f.ap.qualcomm.com>
Date: Fri, 20 Sep 2019 02:55:08 +0000
From: Wen Gong <wgong@....qualcomm.com>
To: "kvalo@...eaurora.org" <kvalo@...eaurora.org>,
Brian Norris <briannorris@...omium.org>
CC: linux-wireless <linux-wireless@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
"ath10k@...ts.infradead.org" <ath10k@...ts.infradead.org>,
Wen Gong <wgong@...eaurora.org>
Subject: RE: [PATCH v3] ath10k: support NET_DETECT WoWLAN feature
> -----Original Message-----
> From: ath10k <ath10k-bounces@...ts.infradead.org> On Behalf Of Kalle Valo
> Sent: Wednesday, September 18, 2019 10:03 PM
> To: Brian Norris <briannorris@...omium.org>
> Cc: linux-wireless <linux-wireless@...r.kernel.org>; Linux Kernel <linux-
> kernel@...r.kernel.org>; ath10k@...ts.infradead.org; Wen Gong
> <wgong@...eaurora.org>
> Subject: [EXT] Re: [PATCH v3] ath10k: support NET_DETECT WoWLAN feature
>
> So essentially the problem is that with firmwares supporting both
> WMI_SERVICE_NLO and WMI_SERVICE_SPOOF_MAC_SUPPORT ath10k
> enables
> NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR, but
> NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR is not enabled
> which is
> inconsistent from user space point of view. Is my understanding correct?
>
> Wen, can you enable NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR?
> Does firmware
> support that?
Yes, I test again, it is enabled NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR now.
>
> _______________________________________________
> ath10k mailing list
> ath10k@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/ath10k
Powered by blists - more mailing lists