From: Sathishkumar Muruganandam <murugana@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [EXT] Re: [PATCH v2 0/2] add Wide Band Scan support
Date: Thu, 14 Nov 2019 18:03:59 +0530 [thread overview]
Message-ID: <2354c9e9f86b2207d6828b45e4055191@codeaurora.org> (raw)
In-Reply-To: <aa0257b408dc7ad6d5f457ac611e76059549737b.camel@sipsolutions.net>
On 2019-11-14 12:08, Johannes Berg wrote:
> On Mon, 2019-11-11 at 13:27 +0530, Sathishkumar Muruganandam wrote:
>>
>> > How is this related to scanning? It sounds to me like you're just
>> > (ab)using scan as a somewhat convenient "do some channel hopping" API
>> > ...
>> >
>>
>> Whether this can be used under "iw offchannel" with
>> NL80211_CMD_REMAIN_ON_CHANNEL?
>
> Are you asking if I would accept wide
> channel extensions to R-O-C?
Yes, adding bandwidth config to existing command.
Something like this,
iw offchannel <freq> [HT40+|HT40-|80MHz] <duration>
> Still I guess I'd like to see an actual reason for it.
Wide band scan is actually moving to a off-channel for a
specified duration to capture 40, 80Mhz data frames.
So, I hope offchannel would accommodate this extension.
--
Thanks,
Sathishkumar
_______________________________________________
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
WARNING: multiple messages have this Message-ID (diff)
From: Sathishkumar Muruganandam <murugana@codeaurora.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, ath11k@lists.infradead.org
Subject: Re: [EXT] Re: [PATCH v2 0/2] add Wide Band Scan support
Date: Thu, 14 Nov 2019 18:03:59 +0530 [thread overview]
Message-ID: <2354c9e9f86b2207d6828b45e4055191@codeaurora.org> (raw)
In-Reply-To: <aa0257b408dc7ad6d5f457ac611e76059549737b.camel@sipsolutions.net>
On 2019-11-14 12:08, Johannes Berg wrote:
> On Mon, 2019-11-11 at 13:27 +0530, Sathishkumar Muruganandam wrote:
>>
>> > How is this related to scanning? It sounds to me like you're just
>> > (ab)using scan as a somewhat convenient "do some channel hopping" API
>> > ...
>> >
>>
>> Whether this can be used under "iw offchannel" with
>> NL80211_CMD_REMAIN_ON_CHANNEL?
>
> Are you asking if I would accept wide
> channel extensions to R-O-C?
Yes, adding bandwidth config to existing command.
Something like this,
iw offchannel <freq> [HT40+|HT40-|80MHz] <duration>
> Still I guess I'd like to see an actual reason for it.
Wide band scan is actually moving to a off-channel for a
specified duration to capture 40, 80Mhz data frames.
So, I hope offchannel would accommodate this extension.
--
Thanks,
Sathishkumar
next prev parent reply other threads:[~2019-11-14 12:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 12:09 [PATCH v2 0/2] add Wide Band Scan support Sathishkumar Muruganandam
2019-11-04 12:09 ` Sathishkumar Muruganandam
2019-11-04 12:09 ` [PATCH v2 1/2] nl80211: " Sathishkumar Muruganandam
2019-11-04 12:09 ` Sathishkumar Muruganandam
2019-11-04 12:09 ` [PATCH v2 2/2] ath11k: " Sathishkumar Muruganandam
2019-11-04 12:09 ` Sathishkumar Muruganandam
2019-11-04 12:11 ` [PATCH v2 0/2] " Johannes Berg
2019-11-04 12:11 ` Johannes Berg
2019-11-05 10:21 ` [EXT] " Sathishkumar Muruganandam
2019-11-05 10:21 ` Sathishkumar Muruganandam
2019-11-05 10:22 ` Johannes Berg
2019-11-05 10:22 ` Johannes Berg
2019-11-11 7:57 ` Sathishkumar Muruganandam
2019-11-11 7:57 ` Sathishkumar Muruganandam
2019-11-14 6:38 ` Johannes Berg
2019-11-14 6:38 ` Johannes Berg
2019-11-14 12:33 ` Sathishkumar Muruganandam [this message]
2019-11-14 12:33 ` Sathishkumar Muruganandam
2019-11-22 12:45 ` Johannes Berg
2019-11-22 12:45 ` Johannes Berg
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=2354c9e9f86b2207d6828b45e4055191@codeaurora.org \
--to=murugana@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=johannes@sipsolutions.net \
--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.