[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <875e2b0c-589b-e13c-2238-c65bd6e2d585@broadcom.com>
Date: Sat, 21 Oct 2023 20:27:35 +0200
From: Arend van Spriel <arend.vanspriel@...adcom.com>
To: Jeff Johnson <quic_jjohnson@...cinc.com>,
Daniel Berlin <dberlin@...rlin.org>,
Arend van Spriel <aspriel@...il.com>,
Franky Lin <franky.lin@...adcom.com>,
Hante Meuleman <hante.meuleman@...adcom.com>
Cc: linux-wireless@...r.kernel.org,
brcm80211-dev-list.pdl@...adcom.com,
SHA-cyfmac-dev-list@...ineon.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] [brcmfmac] Add support for encoding/decoding 6g
chanspecs
On 10/20/2023 11:46 PM, Jeff Johnson wrote:
> On 10/20/2023 2:57 AM, Arend van Spriel wrote:
>> On 10/19/2023 3:42 AM, Daniel Berlin wrote:
>>> This patch adds support for 6G chanspecs, as part of adding 6G and
>>> 802.11ax support.
>
> In ath drivers we are actively discouraging the use of "G" since 1) that
> is not the SI unit for gigahertz, and 2) it conflicts with the use of
> that term in cellular communication where it refers to the generation of
> technology. So I'd recommend using GHz in descriptions/comments and
> GHZ/ghz in identifiers.
I understand, but I am not going to push back on it. The identifiers
using this are defined and used in the firmware API so at least those I
prefer to keep similar/same. For comments in the driver code we should
consider using GHz instead.
> Side note: in USA, Comcast have started promoting their network as
> "10G". In their case they're referring to 10 Gbps speeds. They are being
> called out for misleading consumers with that terminology.
> <https://arstechnica.com/tech-policy/2023/10/comcast-should-stop-advertising-slower-speeds-as-10g-industry-group-says/>
If consumers are that stupid they can mislead by anything ;-)
Thanks,
Arend
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4219 bytes)
Powered by blists - more mailing lists