From: "John W. Linville" <linville@tuxdriver.com>
To: Bing Zhao <bzhao@marvell.com>
Cc: Ben Greear <greearb@candelatech.com>,
Kalle Valo <kvalo@adurom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Amitkumar Karwar <akarwar@marvell.com>,
Avinash Patil <patila@marvell.com>,
Yogesh Powar <yogeshp@marvell.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Frank Huang <frankh@marvell.com>,
Paul Stewart <pstew@chromium.org>
Subject: Re: [PATCH] mwifiex: Add module parameter for regdomain
Date: Thu, 13 Jun 2013 13:30:02 -0400 [thread overview]
Message-ID: <20130613173002.GC3246@tuxdriver.com> (raw)
In-Reply-To: <477F20668A386D41ADCC57781B1F70430EA268B4A3@SC-VEXCH1.marvell.com>
On Wed, Jun 12, 2013 at 12:01:23PM -0700, Bing Zhao wrote:
>
> > >> "iw reg set XX" or "country_code=XX" in hostapd.conf is a *user* hint.
> > >>
> > >> What we need here is a *driver* hint. Furthermore, with a driver
> > >> regulatory hint, the passive-scan and no-ibss flags are cleared so we
> > >> can start AP with hostapd on 5G band.
> > >
> > > So it's a driver hint which is coming from user space via a module
> > > parameter. IMHO you are abusing interfaces here. Is there any better way
> > > to solve your problem?
> >
> > It would be nice to have some way to do this for ath9k and other NICs
> > as well. Best I could come up with is a similar hack for ath9k.
> >
> > I think part of the problem is that this config info needs to be
> > available very early in the module loading/init logic, so it's
> > too late to be configured using 'iw' or similar.
>
> Exactly. regulatory_hint () needs to be called right after wiphy registration.
It does seem a bit ugly. But if Marvell wants it, I don't see any
"regulatory" argument to disallow something like this.
Does anyone have a better suggestion for a user interface for such
a feature?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-06-13 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 22:40 [PATCH] mwifiex: Add module parameter for regdomain Bing Zhao
2013-06-12 7:15 ` Kalle Valo
2013-06-12 17:43 ` Bing Zhao
2013-06-12 18:52 ` Kalle Valo
2013-06-12 18:55 ` Ben Greear
2013-06-12 19:01 ` Bing Zhao
2013-06-13 17:30 ` John W. Linville [this message]
2013-06-13 17:33 ` Paul Stewart
2013-06-13 17:35 ` Paul Stewart
2013-06-13 17:46 ` Bing Zhao
2013-06-13 17:36 ` Ben Greear
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=20130613173002.GC3246@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akarwar@marvell.com \
--cc=bzhao@marvell.com \
--cc=frankh@marvell.com \
--cc=greearb@candelatech.com \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.com \
--cc=patila@marvell.com \
--cc=pstew@chromium.org \
--cc=yogeshp@marvell.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;
as well as URLs for NNTP newsgroup(s).