[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pnjvctjh.fsf@codeaurora.org>
Date: Fri, 20 Sep 2019 10:32:02 +0300
From: Kalle Valo <kvalo@...eaurora.org>
To: Wen Gong <wgong@....qualcomm.com>
Cc: Brian Norris <briannorris@...omium.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
"ath10k\@lists.infradead.org" <ath10k@...ts.infradead.org>,
Wen Gong <wgong@...eaurora.org>
Subject: Re: [PATCH v3] ath10k: support NET_DETECT WoWLAN feature
Wen Gong <wgong@....qualcomm.com> writes:
>> -----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.
Sorry, I'm not quite understanding your reply.
But I mixed up the flags. I meant that can we enable
NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR in ath10k? Does the firmware
releases which have WMI_SERVICE_NLO support
NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR as well?
--
Kalle Valo
Powered by blists - more mailing lists