Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Arik Nemtsov <arik@wizery.com>
Cc: "Luis R. Rodriguez" <mcgrof@suse.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v5 2/4] cfg80211: allow usermode to query wiphy specific regdom
Date: Sun, 30 Nov 2014 13:32:11 +0100	[thread overview]
Message-ID: <1417350731.2156.1.camel@sipsolutions.net> (raw)
In-Reply-To: <CA+XVXffyFiqE31KLN2Os1Uu5z9FrFPXXs0Qs_D+OEfnqjgd8uQ@mail.gmail.com> (sfid-20141130_132705_637056_A05DED9F)

On Sun, 2014-11-30 at 14:26 +0200, Arik Nemtsov wrote:

> I think Johannes' point was that it's easy to overrun the message size
> if there are a lot of wiphys.

Yes.

> So I'll simply add an iterator over all wiphys in "iw reg get" and
> kernel-mode will only return a single regdomain in each GET_REG
> invocation.

Err, there's such a thing built into netlink already - just support
dumpit instead of doit :)
iw will have to fall back to doit for older kernels though I guess.

> About the "--all" suggestion - I think it's fine to not have backward
> compatibility in the output of "iw reg get"? So we can just output the
> global first, and then output private regdoms for all wiphys that have
> them.
> 
> Does that sound ok?

Yeah I wasn't taking about the iw display, and adding --all there
doesn't help for what I was concerned about.

> Well you have to give a wiphy-idx in order to get a private regdom in
> the first place. And only new userspace will add a wiphy-idx in the
> first place..

Are you sure about the last part though? wpa_supplicant often passed a
netdev index instead of a wiphy index for example, so I could imagine it
passing a wiphy index here even though it was previously ignored?

If it didn't though then I think there's no problem, there shouldn't
really be any userspace other than wpa_s and iw for this I guess/hope.

johannes


  reply	other threads:[~2014-11-30 12:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  7:44 [PATCH v5 1/4] cfg80211: leave invalid channels on regdomain change Arik Nemtsov
2014-11-27  7:44 ` [PATCH v5 2/4] cfg80211: allow usermode to query wiphy specific regdom Arik Nemtsov
2014-11-28 13:46   ` Johannes Berg
2014-11-28 22:00     ` Luis R. Rodriguez
2014-11-30 12:26       ` Arik Nemtsov
2014-11-30 12:32         ` Johannes Berg [this message]
2014-11-30 12:36           ` Arik Nemtsov
2014-11-28 22:03   ` Luis R. Rodriguez
2014-11-27  7:44 ` [PATCH v5 3/4] cfg80211: allow wiphy specific regdomain management Arik Nemtsov
2014-11-28 13:53   ` Johannes Berg
2014-11-27  7:44 ` [PATCH v5 4/4] cfg80211: return private regdom for self-managed devices Arik Nemtsov
2014-11-28 13:57   ` Johannes Berg
2014-11-28 13:44 ` [PATCH v5 1/4] cfg80211: leave invalid channels on regdomain change Johannes Berg

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=1417350731.2156.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=arik@wizery.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@suse.com \
    /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