From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Daniel Berlin <dberlin@dberlin.org>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
SHA-cyfmac-dev-list@infineon.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] [brcmfmac] Add support for encoding/decoding 6g chanspecs
Date: Sat, 21 Oct 2023 20:27:35 +0200 [thread overview]
Message-ID: <875e2b0c-589b-e13c-2238-c65bd6e2d585@broadcom.com> (raw)
In-Reply-To: <060a8bd0-6470-4d75-a5bb-e012c3e7cb3d@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
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
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4219 bytes --]
next prev parent reply other threads:[~2023-10-21 18:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1697650207.git.dberlin@dberlin.org>
[not found] ` <0b95944fcf047b3ec83cecb0c65ca24de43810fd.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:57 ` [PATCH 1/5] [brcmfmac] Add support for encoding/decoding 6g chanspecs Arend van Spriel
2023-10-20 16:36 ` Daniel Berlin
2023-10-20 21:46 ` Jeff Johnson
2023-10-21 18:27 ` Arend van Spriel [this message]
[not found] ` <52c993fd93e13ac015be935a5284294c9a74ea8e.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:58 ` [PATCH 2/5] [brcmfmac] Add support for 6G bands Arend van Spriel
2023-10-20 16:35 ` Daniel Berlin
2023-10-20 18:37 ` Arend van Spriel
2023-10-23 11:41 ` Daniel Berlin
2023-10-23 18:06 ` Arend Van Spriel
2023-10-23 18:09 ` Arend Van Spriel
[not found] ` <9bb36bcc0dbbbe6f991be30ec404b6e5197238ac.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:58 ` [PATCH 3/5] wifi: brcmfmac: Add support for SCAN_V3 Arend van Spriel
[not found] ` <079882bf4a7c026547ecf8ad50a2b7a49ade7130.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:59 ` [PATCH 4/5] wifi: brcmfmac: Support bss_info up to v112 Arend van Spriel
2023-10-20 17:31 ` Daniel Berlin
2023-10-31 14:04 ` Daniel Berlin
2023-10-31 16:27 ` Arend Van Spriel
2023-11-07 11:11 ` Hector Martin
2023-11-07 11:51 ` Arend van Spriel
2023-11-07 12:00 ` Daniel Berlin
2023-11-07 19:28 ` Arend van Spriel
[not found] ` <791863a231dca48234a3468b299d0bc71a85b6b0.1697650207.git.dberlin@dberlin.org>
2023-10-20 9:59 ` [PATCH 5/5] [brcmfmac] Add remaining support for 6G by supporting new scan structures Arend van Spriel
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=875e2b0c-589b-e13c-2238-c65bd6e2d585@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=dberlin@dberlin.org \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox