From: "Greenman, Gregory" <gregory.greenman@intel.com>
To: "chiluk@ubuntu.com" <chiluk@ubuntu.com>
Cc: "regressions@leemhuis.info" <regressions@leemhuis.info>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>,
"marcel@holtmann.org" <marcel@holtmann.org>
Subject: Re: [regression] Bug 216753 - 6e 6 ghz bands are disabled since 5.16 on intel ax211
Date: Thu, 19 Jan 2023 14:09:18 +0000 [thread overview]
Message-ID: <bc0b159321826c0336f074ca23244fc0cde507f2.camel@intel.com> (raw)
In-Reply-To: <CAMfi-DQYU3WQk8x-GFieexEE_enRDe4J0AzyZHk9rtRykpUEnA@mail.gmail.com>
On Fri, 2023-01-06 at 09:37 -0600, Dave Chiluk wrote:
> On Thu, Jan 5, 2023 at 12:15 AM Greenman, Gregory
> <gregory.greenman@intel.com> wrote:
> >
> > I'll try to explain, the problem here is not technical. After some
> > internal checks, it appears that we (wifi driver) aren't allowed to
> > decide if 6E should be enabled or not. Because of the legal restrictions,
> > OEM should make this decision and enable/disable 6E in the BIOS. This
> > commit only gets the value from the BIOS and configures the firmware
> > accordingly. So, unfortunately, legal restriction is the reason we cannot
> > revert/overwrite 6E enablement...
> >
> Thank you Gregory, I've been reading between the lines, and this is
> pretty much what I expected you to say. So in the past when
> OEMs/systems manufacturers have been irresponsible/inept like this we
> have implemented flags to force ignore the values coming out of the
> bios. As it's now obvious that the problem here is a legal/regulatory
> issue, I'd hope that having a force flag would be acceptable from a
> that perspective. I'm no lawyer, but I expect once a user decides to
> explicitly set a force flag to ignore the bios values I'd suspect the
> responsibility would shift from the manufacturers and back onto the
> user.
>
> Would such a patch be theoretically acceptable? If so I'll write up a
> patch to do this and submit it next week hopefully.
Sorry for the long delay...
We looked at it again and this particular scenario looks more like some
bug maybe in the firmware since in US it should be enabled by default.
Can I ask to collect a trace-cmd dump for the case when it doesn't
work with "-e iwlwifi -e mac80211 -e cfg80211 -e iwlwifi_msg"?
prev parent reply other threads:[~2023-01-19 14:26 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
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 [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=bc0b159321826c0336f074ca23244fc0cde507f2.camel@intel.com \
--to=gregory.greenman@intel.com \
--cc=chiluk@ubuntu.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).