From: Sven Eckelmann <sven@narfation.org>
To: luciano.coelho@intel.com,
Sharadanand Karanjkar <sk@simonwunderlich.de>,
johannes.berg@intel.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwlwifi: ax210: 6GHz channels disabled in Germany by firmware
Date: Sat, 30 Oct 2021 19:17:38 +0200 [thread overview]
Message-ID: <6520824.1yIjQniEF0@sven-l14> (raw)
In-Reply-To: <dd512568-9d9f-289a-bc7b-9b6dfc1c0c8a@simonwunderlich.de>
[-- Attachment #1: Type: text/plain, Size: 2129 bytes --]
On Friday, 29 October 2021 16:55:16 CEST Sharadanand Karanjkar wrote:
> > We are using Intels "ax210ngw" card with "iwlwifi-ty-a0-gf-a0-66.ucode"
> > firmware, we are using the kernel from "5.15.0-rc7" tag.
Would have been nice to have some info about the relevant components directly
in the subject. And iw is not that relevant - it is just a tool which you used
to inspect the state of the system. I have therefore adjusted the subject
slightly
> > The problem we are facing is we are not able to enable 6GHz channels
> > for Germany region. Following is the output for "iw reg get"
> >
[....]
> >
> > The iw phy# info also shows that the 6GHz channels are not enabled. We
> > have found one commit which is included in the "5.15.0-rc7" tag which
> > indicates that 6Ghz channels are now supported in the driver.
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=cdf854d2ddca01bf126ac138a8ee3e5d6320086f
This is not part of the driver. But the kernel might use it - like in your
example. Unfortunately, the previously mentioned firmware includes an own
regulatory db which is then used for the phy0 ("self managed").
But the commit at least provides some good reasons why Intel might consider
enabling the indoor channel in the frequency range 5945 - 6425 MHz. It would
therefore be nice to know whether/when Intel actually has plans to enable
these channels in Germany (and not only for the US) in the near future. Maybe
there are even newer (test) firmware versions available but I am not aware
of any newer firmware version than the previously mentioned one [1].
And this firmware was published for linux-firmware right around the time when
Vfg. 55/2021 was released - so it is to some extend expected that Intel didn't
yet incorporated such a change.
I only saw newer releases for other HW [2] but not for Ty.
Kind regards,
Sven
[1] https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=5de082d4d0f2db7722c9e6f5c9cff1fefd8073be
[2] https://chromium-review.googlesource.com/c/chromiumos/third_party/linux-firmware/+/3159525
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-30 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <57f467ec-074c-8260-7872-84eccfdcc1c7@simonwunderlich.de>
2021-10-29 14:55 ` iw reg get Not showing 6GHz channels in Germany Sharadanand Karanjkar
2021-10-30 17:17 ` Sven Eckelmann [this message]
2021-11-01 14:58 ` iwlwifi: ax210: 6GHz channels disabled in Germany by firmware Sven Eckelmann
2021-11-02 7:59 ` Sven Eckelmann
2021-11-13 8:23 ` Sven Eckelmann
2022-01-11 10:25 ` Sven Eckelmann
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=6520824.1yIjQniEF0@sven-l14 \
--to=sven@narfation.org \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=sk@simonwunderlich.de \
/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