From: Maxime Bizon <mbizon@freebox.fr>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Dave Chiluk <chiluk@ubuntu.com>,
Marcel Holtmann <marcel@holtmann.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>,
"Greenman, Gregory" <gregory.greenman@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211
Date: Tue, 20 Dec 2022 14:16:16 +0100 [thread overview]
Message-ID: <20221220131616.GE25155@sakura> (raw)
In-Reply-To: <0611323c-2088-e6f3-1c38-7cf742dfb60d@leemhuis.info>
On Sunday 04 Dec 2022 à 10:37:42 (+0100), Thorsten Leemhuis wrote:
> That makes me (as a outsider that has no real knowledge about the inner
> workings of the Linux Wifi subsystem) wonder: Does it work in Windows?
No it does not.
More precisely, it used to work with older Intel drivers that (I
suppose) ignored this.
But starting from I don't remember which version it stopped working,
same behaviour as Linux.
--
Maxime
next prev parent reply other threads:[~2022-12-20 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 10:14 [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211 Thorsten Leemhuis
2022-12-01 11:33 ` Coelho, Luciano
2022-12-02 15:37 ` Dave Chiluk
2022-12-02 16:02 ` Thorsten Leemhuis
2022-12-02 16:46 ` Marcel Holtmann
2022-12-02 17:18 ` Dave Chiluk
2022-12-02 17:42 ` Maxime Bizon
2022-12-04 9:37 ` Thorsten Leemhuis
2022-12-20 13:16 ` Maxime Bizon [this message]
2023-01-03 19:48 ` Dave Chiluk
2022-12-02 17:46 ` Marcel Holtmann
2022-12-05 16:35 ` Dave Chiluk
2023-01-03 17:37 ` Dave Chiluk
2023-01-04 8:50 ` Coelho, Luciano
2023-01-05 6:15 ` Greenman, Gregory
2023-01-06 15:37 ` Dave Chiluk
2023-01-19 14:09 ` Greenman, Gregory
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=20221220131616.GE25155@sakura \
--to=mbizon@freebox.fr \
--cc=chiluk@ubuntu.com \
--cc=gregory.greenman@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=marcel@holtmann.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).