Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <14722778-dda0-cb9f-8647-892493d94a5c@leemhuis.info>
 <2026016246ef719605c9932feeb56b105833593b.camel@intel.com>
 <CAMfi-DRE-u5TNu2zAL-7A-ENHM9EiJeYJ38BL_FMdk6QmW7c9w@mail.gmail.com>
 <9a03c244-adff-afaf-7385-d8e89cd3f338@leemhuis.info> <02F8DDF1-EC0D-4EBD-88F5-7E000841C337@holtmann.org>
 <CAMfi-DQfuro4c_VUrFHBTv8sPnwuV8XhTV_W7qswGeCC2t-wzg@mail.gmail.com>
 <19ea39c87df3c54cbc487466f806bc157d0bf563.camel@freebox.fr> <0611323c-2088-e6f3-1c38-7cf742dfb60d@leemhuis.info>
In-Reply-To: <0611323c-2088-e6f3-1c38-7cf742dfb60d@leemhuis.info>
From:   Dave Chiluk <chiluk@ubuntu.com>
Date:   Tue, 3 Jan 2023 13:48:23 -0600
Message-ID: <CAMfi-DTyhv=Pga+ds5REtxngwoXeufMYr_dOh93X75Pm9bbU0w@mail.gmail.com>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16
 on intel ax211
To:     Thorsten Leemhuis <regressions@leemhuis.info>
Cc:     mbizon@freebox.fr, 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>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sun, Dec 4, 2022 at 3:37 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> Does it work in Windows?

That's an interesting question.  I did some searching and apparently a
number of other OEMs are all having issues with this even under
windows.
https://www.dell.com/community/XPS/Does-the-XPS-9520-support-Wi-Fi6E-6GHz/td-p/8229808
https://www.reddit.com/r/framework/comments/t0ghsc/fix_for_6_ghz_wifi_on_the_intel_ax210/
If I had to guess, I'd suspect that Intel has pushed similar checking
of ACPI into the windows driver.

Can we just get this terrible code ripped out until the OEMs get their
act together?  This is really bad user experience.