From: Johannes Berg <johannes@sipsolutions.net>
To: wens@kernel.org, Mohammed.Al-Obaidi@badraproject.com
Cc: wireless-regdb@lists.infradead.org,
linux-wireless@vger.kernel.org, mnewiraq2000@gmail.com,
mnew_iraq@yahoo.com
Subject: Re: [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ)
Date: Tue, 19 May 2026 10:55:07 +0200 [thread overview]
Message-ID: <21a4cc48403b338311ea0ff76d757893b1f765cd.camel@sipsolutions.net> (raw)
In-Reply-To: <CAGb2v66mCBP8KiMF3nRTix_zYDhsb_o4KNj-7-enB0+ULvh0_A@mail.gmail.com>
Hi,
> As for 10 MHz, I don't think it is supported, so we don't really consider
> that case. I could be wrong though.
>
> Johannes, could you shed some light on 10 MHz channel width support?
It's ... complicated?
We support a _very_ limited set of 5/10 MHz operation, but I think most
of it is fairly much unreachable from userspace. I asked about removing
it entirely a few years ago, and some people were opposed, but said
people also haven't actually helped take care of it or anything ... I
was just tempted again a little while back to remove it due to the rates
issues.
Ever since my commit 5add321c329b ("wifi: cfg80211: remove scan_width
support") I believe it has been unreachable on the *client* side, but
given that we still have some support in _nl80211_parse_chandef() and
chandef functions, I expect that it would be possible to still configure
an AP or monitor interface with 5/10 MHz, though only with drivers that
have WIPHY_FLAG_SUPPORTS_5_10_MHZ, i.e. ath5k, ath9k and hwsim. I
wouldn't mind removing it all though.
Is this a concern from a regulatory POV right now, due to say power
density by channel width? This feels somewhat familiar even with higher
channel widths - maybe it's time to add such an attribute to the regdb?
johannes
next prev parent reply other threads:[~2026-05-19 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1886262646.6291779.1777997531793.ref@mail.yahoo.com>
2026-05-05 16:12 ` [PATCH] wireless-regdb: add regulatory rules for Iraq (IQ) Mohammed Abdalla
2026-05-16 7:42 ` Mohammed.Al-Obaidi
2026-05-19 7:14 ` Chen-Yu Tsai
2026-05-19 8:55 ` Johannes Berg [this message]
2026-05-19 8:59 ` Chen-Yu Tsai
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=21a4cc48403b338311ea0ff76d757893b1f765cd.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Mohammed.Al-Obaidi@badraproject.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mnew_iraq@yahoo.com \
--cc=mnewiraq2000@gmail.com \
--cc=wens@kernel.org \
--cc=wireless-regdb@lists.infradead.org \
/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