From: Johannes Berg <johannes@sipsolutions.net>
To: "Rameshkumar Sundaram (QUIC)" <quic_ramess@quicinc.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath11k@lists.infradead.org" <ath11k@lists.infradead.org>
Subject: Re: [PATCH 1/2] mac80211: add support to configure 6GHz non-ht duplicate transmission
Date: Mon, 21 Mar 2022 09:58:16 +0100 [thread overview]
Message-ID: <a537c6e02afbfa26eec2a54dbd8bc649f77ae3a3.camel@sipsolutions.net> (raw)
In-Reply-To: <DM6PR02MB4937C53041172E9A52846A0BE9169@DM6PR02MB4937.namprd02.prod.outlook.com>
On Mon, 2022-03-21 at 05:12 +0000, Rameshkumar Sundaram (QUIC) wrote:
>
> >
> > I am wondering though if this should even be detected from the HE
> > operation element itself, rather than from the beacon rate settings
> > that are
> > separate in nl80211?
> This is a BW dependent bit in HE Oper IE and user space can switch BW
> (CSA/chan switch scenarios).
> Which can call assign_beacon directly, Hence adding the logic here to
> cover all Beacon change cases.
>
Yeah but still ... why do we take it from the content rather than adding
a control for it?
johannes
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2022-03-21 8:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 8:42 [PATCH 0/2] Add support to configure 6GHz non-ht duplicate transmission Rameshkumar Sundaram
2022-02-15 8:43 ` [PATCH 1/2] mac80211: add " Rameshkumar Sundaram
2022-03-11 11:03 ` Johannes Berg
2022-03-21 5:12 ` Rameshkumar Sundaram (QUIC)
2022-03-21 8:58 ` Johannes Berg [this message]
2022-03-22 13:50 ` Rameshkumar Sundaram (QUIC)
2022-03-22 15:04 ` Johannes Berg
2022-04-17 14:30 ` Rameshkumar Sundaram (QUIC)
2022-05-04 11:47 ` Johannes Berg
2022-02-15 8:43 ` [PATCH 2/2] ath11k: " Rameshkumar Sundaram
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=a537c6e02afbfa26eec2a54dbd8bc649f77ae3a3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_ramess@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