All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>, cjhuang@codeaurora.org
Cc: Brian Norris <briannorris@chromium.org>,
	linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/2] ath10k: support MAC address randomization in scan
Date: Fri, 13 Apr 2018 23:13:32 +0200	[thread overview]
Message-ID: <5AD11D7C.1030603@broadcom.com> (raw)
In-Reply-To: <877epbs5v7.fsf@kamboji.qca.qualcomm.com>

On 4/13/2018 1:28 PM, Kalle Valo wrote:
> cjhuang@codeaurora.org writes:
>
>>>> +	if (test_bit(WMI_SERVICE_SPOOF_MAC_SUPPORT, ar->wmi.svc_map)) {
>>>> +		ret = ath10k_wmi_scan_prob_req_oui(ar, ar->mac_addr);
>>>> +		if (ret) {
>>>> +			ath10k_err(ar, "failed to set prob req oui: %i\n", ret);
>>>> +			goto err_dfs_detector_exit;
>>>> +		}
>>>> +
>>>> +		ar->hw->wiphy->features |=
>>>> +			NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR;
>>>
>>> Do you support NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR too?
>>
>> I'll add this flag too.
>
> Are you going to send v2 or what's the plan?

Maybe a stupid question, but does ath10k support scheduled scan?

Regards,
Arend

WARNING: multiple messages have this Message-ID (diff)
From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Kalle Valo <kvalo@codeaurora.org>, cjhuang@codeaurora.org
Cc: Brian Norris <briannorris@chromium.org>,
	linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 2/2] ath10k: support MAC address randomization in scan
Date: Fri, 13 Apr 2018 23:13:32 +0200	[thread overview]
Message-ID: <5AD11D7C.1030603@broadcom.com> (raw)
In-Reply-To: <877epbs5v7.fsf@kamboji.qca.qualcomm.com>

On 4/13/2018 1:28 PM, Kalle Valo wrote:
> cjhuang@codeaurora.org writes:
>
>>>> +	if (test_bit(WMI_SERVICE_SPOOF_MAC_SUPPORT, ar->wmi.svc_map)) {
>>>> +		ret = ath10k_wmi_scan_prob_req_oui(ar, ar->mac_addr);
>>>> +		if (ret) {
>>>> +			ath10k_err(ar, "failed to set prob req oui: %i\n", ret);
>>>> +			goto err_dfs_detector_exit;
>>>> +		}
>>>> +
>>>> +		ar->hw->wiphy->features |=
>>>> +			NL80211_FEATURE_SCAN_RANDOM_MAC_ADDR;
>>>
>>> Do you support NL80211_FEATURE_SCHED_SCAN_RANDOM_MAC_ADDR too?
>>
>> I'll add this flag too.
>
> Are you going to send v2 or what's the plan?

Maybe a stupid question, but does ath10k support scheduled scan?

Regards,
Arend


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  reply	other threads:[~2018-04-13 21:13 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30  3:13 [PATCH 0/2] ath10k: support MAC address randomization in scan Carl Huang
2018-03-30  3:13 ` Carl Huang
2018-03-30  3:13 ` [PATCH 1/2] ath10k: Add WMI_SERVICE_AVAILABLE_EVENT support Carl Huang
2018-03-30  3:13   ` Carl Huang
2018-04-16 13:40   ` [1/2] " Kalle Valo
2018-04-16 13:40   ` Kalle Valo
2018-04-24  5:46   ` Kalle Valo
2018-04-24  5:46   ` Kalle Valo
2018-03-30  3:14 ` [PATCH 2/2] ath10k: support MAC address randomization in scan Carl Huang
2018-03-30  3:14   ` Carl Huang
2018-04-12 20:59   ` Brian Norris
2018-04-12 20:59     ` Brian Norris
2018-04-13  6:53     ` cjhuang
2018-04-13  6:53       ` cjhuang
2018-04-13 11:28       ` Kalle Valo
2018-04-13 11:28         ` Kalle Valo
2018-04-13 21:13         ` Arend van Spriel [this message]
2018-04-13 21:13           ` Arend van Spriel
2018-04-16  5:16           ` cjhuang
2018-04-16  5:16             ` cjhuang
2018-04-16 11:32             ` Kalle Valo
2018-04-16 11:32               ` Kalle Valo
2018-04-17  0:28               ` Brian Norris
2018-04-17  0:28                 ` Brian Norris
2018-04-17  8:22                 ` Arend van Spriel
2018-04-17  8:22                   ` Arend van Spriel
2018-04-17 16:07                   ` Brian Norris
2018-04-17 16:07                     ` Brian Norris
2018-04-17 21:49                     ` Arend van Spriel
2018-04-17 21:49                       ` Arend van Spriel
2018-04-17 22:26                       ` Brian Norris
2018-04-17 22:26                         ` Brian Norris
2018-04-18  2:35                         ` Dan Williams
2018-04-18  2:35                           ` Dan Williams
2018-04-18  8:29                           ` Arend van Spriel
2018-04-18  8:29                             ` Arend van Spriel
2018-04-18  9:58                             ` Johannes Berg
2018-04-18  9:58                               ` Johannes Berg
2018-04-16  5:17         ` cjhuang
2018-04-16  5:17           ` cjhuang
2018-04-16 13:42   ` [2/2] " Kalle Valo
2018-04-16 13:42   ` Kalle Valo
     [not found]   ` <20180416134238.B16596076A@smtp.codeaurora.org>
2018-04-17  7:29     ` cjhuang
2018-04-17  7:29       ` cjhuang
2018-04-20 10:30       ` Kalle Valo
2018-04-20 10:30         ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5AD11D7C.1030603@broadcom.com \
    --to=arend.vanspriel@broadcom.com \
    --cc=ath10k@lists.infradead.org \
    --cc=briannorris@chromium.org \
    --cc=cjhuang@codeaurora.org \
    --cc=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.