Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <9f992ca7731f966fdc45a38a13c202898e92f2b2.camel@sipsolutions.net>
Subject: Re: [PATCH] mac80211: Fix radiotap header channel flag for 6GHz band
From:   Johannes Berg <johannes@sipsolutions.net>
To:     Aloka Dixit <alokad@codeaurora.org>
Cc:     linux-wireless@vger.kernel.org,
        linux-wireless-owner@vger.kernel.org
Date:   Fri, 11 Sep 2020 22:52:58 +0200
In-Reply-To: <010101747eef4d8b-8b5fdae5-790f-4d19-a2df-fba00350baa3-000000@us-west-2.amazonses.com>
References: <010101747ab7b9c0-45fa1c2a-3bb5-44e8-8e6d-457cad2e9845-000000@us-west-2.amazonses.com>
         <1cc7242cd00cd5141a56f17a7f5c80700485aa39.camel@sipsolutions.net>
         <010101747eef4d8b-8b5fdae5-790f-4d19-a2df-fba00350baa3-000000@us-west-2.amazonses.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-1.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

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.

johannes