All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: iwd@lists.01.org
Subject: Re: >=iwd-1.8: crash in dmesg at boot
Date: Tue, 20 Oct 2020 11:42:06 -0500	[thread overview]
Message-ID: <1420f2a8-cbe0-6885-8c15-76f719269f2a@gmail.com> (raw)
In-Reply-To: <d163a616006b4fc97fc7af2048b19d19068ff74e.camel@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

Hi James,

> 
> Side note: wpa_supplicant likely doesn't have this problem since it
> does not include ATTR_WIPHY with its GET_REG call AFAIK. Anyone know if
> GET_REG is intended to be per-phy? Or why we are including ATTR_WIPHY?
> 

from linux/nl80211.h:
"
  @NL80211_CMD_GET_REG: ask the wireless core to send us its currently set 
regulatory domain. If %NL80211_ATTR_WIPHY is specified and the device has a 
private regulatory domain, it will be returned. Otherwise, the global regdomain 
will be returned.

A device will have a private regulatory domain if it uses the regulatory_hint() 
API. Even when a private regdomain is used the channel information will still be 
mended according to further hints from the regulatory core to help with compliance.
"

So looks like wpa_s always requests the global domain, while iwd is in theory 
more correct and requests a per-wiphy one.

Regards,
-Denis

  reply	other threads:[~2020-10-20 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 16:14 >=iwd-1.8: crash in dmesg at boot m1027
2020-10-20 16:28 ` James Prestwood
2020-10-20 16:42   ` Denis Kenzior [this message]
2020-10-21 10:36   ` m1027

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=1420f2a8-cbe0-6885-8c15-76f719269f2a@gmail.com \
    --to=denkenz@gmail.com \
    --cc=iwd@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.