From: Aloka Dixit <alokad@codeaurora.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
linux-wireless-owner@vger.kernel.org
Subject: Re: [PATCH] mac80211: Fix radiotap header channel flag for 6GHz band
Date: Sun, 20 Sep 2020 11:53:43 -0700 [thread overview]
Message-ID: <eb68b253912675a3e4705ad942ce07d8@codeaurora.org> (raw)
In-Reply-To: <1cada267-3ebf-0bac-328a-3abe2c16cd25@broadcom.com>
On 2020-09-14 02:14, Arend Van Spriel wrote:
> On 9/11/2020 10:52 PM, Johannes Berg wrote:
>> On Fri, 2020-09-11 at 20:50 +0000, Aloka Dixit wrote:
>>>
>>>> Not that anything even cares ... so there's no point in adding a
>>>> 6GHz
>>>> flag to radiotap.
>>>>
>>> Separate flag for 6GHz would have been best option, but I still think
>>> better to set 5GHz as 6GHz frequencies start in 5GHz range.
>>
>> But why? wireshark probably needs to be adjusted anyway, so it can
>> just
>> look at the frequency instead? And it would pretend that it's now an
>> "11a" frame ... so that clearly never was important, since that hasn't
>> been true since HT.
>
> It has been couple of month ago that I looked into wireshark about
> this and I think it is already ignoring the band flags and just looks
> at the frequency.
>
> Regards,
> Arend
Ok, thanks for letting me know!
next prev parent reply other threads:[~2020-09-20 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <010101747ab7b9c0-45fa1c2a-3bb5-44e8-8e6d-457cad2e9845-000000@us-west-2.amazonses.com>
2020-09-11 7:36 ` [PATCH] mac80211: Fix radiotap header channel flag for 6GHz band Johannes Berg
2020-09-11 20:50 ` Aloka Dixit
[not found] ` <010101747eef4d8b-8b5fdae5-790f-4d19-a2df-fba00350baa3-000000@us-west-2.amazonses.com>
2020-09-11 20:52 ` Johannes Berg
2020-09-14 9:14 ` Arend Van Spriel
2020-09-20 18:53 ` Aloka Dixit [this message]
2020-09-11 1:11 Aloka Dixit
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=eb68b253912675a3e4705ad942ce07d8@codeaurora.org \
--to=alokad@codeaurora.org \
--cc=arend.vanspriel@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless-owner@vger.kernel.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.