From: Johannes Berg <johannes@sipsolutions.net>
To: Sriram R <srirrama@codeaurora.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] cfg80211: Allow self managed devices to update global regulatory
Date: Fri, 06 Sep 2019 09:44:14 +0200 [thread overview]
Message-ID: <ef59752f56684e6a6850ea12802918f0434abf77.camel@sipsolutions.net> (raw)
In-Reply-To: <1567739733-18852-1-git-send-email-srirrama@codeaurora.org>
On Fri, 2019-09-06 at 08:45 +0530, Sriram R wrote:
> Currently, self managed drivers cannot update the global regulatory
> using a regulatory hint from driver if the wiphy regd is already set
> from other sources.
> Due to this, when a regulatory hint is provided to cfg80211 from
> self managed devices, the request gets ignored and global reg is
> always at default, i.e World reg, DFS-UNSET.
> Hence in such systems, the result of 'iw reg get' does not indicate a
> valid global regd.
Yeah, but ... if you have a self-managed PHY you should anyway use
iw phy0 reg get
instead of plain
iw reg get
so I'm not sure I understand?
johannes
prev parent reply other threads:[~2019-09-06 7:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 3:15 [RFC] cfg80211: Allow self managed devices to update global regulatory Sriram R
2019-09-06 7:44 ` Johannes Berg [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=ef59752f56684e6a6850ea12802918f0434abf77.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=srirrama@codeaurora.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;
as well as URLs for NNTP newsgroup(s).