mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Rio Liu <rio@r26.me>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	 "benjamin.berg@intel.com" <benjamin.berg@intel.com>
Subject: Re: [PATCH] Skip ieee80211_verify_sta_ht_mcs_support check in non-strict mode
Date: Wed, 15 Apr 2026 11:28:38 +0200	[thread overview]
Message-ID: <093e01e4f79f9922f1220f38ceaea4f8448a6d72.camel@sipsolutions.net> (raw)
In-Reply-To: <AKVRf_yEu2mRCJekCJpre5xXMuHa_3_dO7_H1UU8fiKZRjJUf96ZKepiR999NwpiVwmzWBYoKipBpx1rqZatVihMYOCvANUnbeoyI2U7ct0=@r26.me>

On Tue, 2026-04-14 at 05:02 +0000, Rio Liu wrote:
> Some AP advertise 3 or 4 spatial stream MCS indexes in their basic
> HT-MCS set. On cards with lower (2x2) spatial streams, the check would
> fail, and we'd be stuck with no HT when it in fact work fine with
> 2-stream rate. This change makes it so the check is only performed in
> strict mode.
> 
> Signed-off-by: Rio Liu <rio@r26.me>
> ---

Should probably have a Fixes tag for this?

> Link: https://linuxcommunity.io/t/intel-ax210-speeds-capped-at-20-mbps-on-multiple-distros/6708/28
> Link: https://bbs.archlinux.org/viewtopic.php?id=312952
> Link: https://bbs.archlinux.org/viewtopic.php?id=313033
> Link: https://www.reddit.com/r/Rogers/comments/1s89j9f/xb8_5ghz_dfs_channel_broadcasting_at_54_mbps/
> Link: https://www.reddit.com/r/Comcast_Xfinity/comments/1s7fc3f/recent_firmware_update_to_wifi_gateway_breaking/
> Link: https://www.reddit.com/r/Comcast_Xfinity/comments/1sg9r6z/slow_internet_for_linux_computers/

> +	/*
> +	 * Some AP advertise 3 or 4 spatial stream MCS indexes in their basic HT-MCS
> +	 * set. On cards with lower (2x2) spatial streams, the check would fail, and
> +	 * we'd be stuck with no HT when it in fact work fine with 2-stream rate. So
> +	 * check it only in strict mode.
> +	 */
> +	if (!ieee80211_hw_check(&sdata->local->hw, STRICT))
> +		return true;

And generally we prefer to have some indication in the comment which APs
were affected (though I see the VHT one also didn't have that), such as
in ieee80211_verify_peer_he_mcs_support().

johannes

      reply	other threads:[~2026-04-15  9:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-14  4:39 Rio Liu
2026-04-14  5:02 ` Rio Liu
2026-04-15  9:28   ` Johannes Berg [this message]

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=093e01e4f79f9922f1220f38ceaea4f8448a6d72.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=benjamin.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rio@r26.me \
    /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

all inboxes | Powered by JetHome®