linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	wireless <linux-wireless@vger.kernel.org>,
	John Linville <linville@tuxdriver.com>
Subject: Re: ieee80211_regdom module parameter for cfg80211
Date: Wed, 18 Feb 2009 16:38:10 -0600	[thread overview]
Message-ID: <499C8DD2.7000800@lwfinger.net> (raw)
In-Reply-To: <20090218220531.GD4246@tesla>

Luis R. Rodriguez wrote:
> On Wed, Feb 18, 2009 at 01:31:52PM -0800, Johannes Berg wrote:
>> On Wed, 2009-02-18 at 15:29 -0600, Larry Finger wrote:
>>> On at least one forum, I have seen the recommendation that a user set their
>>> regulatory domain by creating the file /etc/modprobe.d/cfg80211 with the
>>> contents "ieee80211_regdom=US".
>>>
>>> That works as long as CONFIG_WIRELESS_OLD_REGULATORY is set in their .config,
>>> but will fail if it is not.
>>>
>>> Should the module_param statement be moved outside the ifdef
>>> CONFIG_WIRELESS_OLD...? Setting the module parameter that way might not make any
>>> sense, but it surely shouldn't kill wireless.
>> I actually see no reason to not just /honour/ it by calling crda with
>> its parameter if CONFIG_WIRELESS_OLD_REGULATORY isn't set.
> 
> The idea was that things we want to get rid of will go in OLD_REG. Static regdoms
> for US, JP and EU fall into that and so does the module parameter. I believe
> it is silly to keep the module parameter around as we already have userspace
> APIs to let users set this.

I guess we leave it the way it is. At least the only people that will get caught
are those that upgrade their distro. A clean install should redo the /etc/...
tree and do away with such modifications.

Larry

  parent reply	other threads:[~2009-02-18 22:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 21:29 ieee80211_regdom module parameter for cfg80211 Larry Finger
2009-02-18 21:31 ` Johannes Berg
2009-02-18 22:05   ` Luis R. Rodriguez
2009-02-18 22:34     ` Gábor Stefanik
2009-02-18 22:45       ` Luis R. Rodriguez
2009-02-18 22:38     ` Larry Finger [this message]
2009-02-18 22:48       ` Luis R. Rodriguez
2009-02-20 19:45         ` Gábor Stefanik
2009-02-20 20:33           ` Luis R. Rodriguez
2009-02-20 21:07             ` Gábor Stefanik
2009-02-20 23:40               ` Luis R. Rodriguez
2009-02-21 15:31                 ` Gábor Stefanik
2009-02-23 17:51                   ` Luis R. Rodriguez
2009-02-23 20:33                     ` Gábor Stefanik
2009-02-23 21:18                       ` Luis R. Rodriguez
2009-02-23 21:36                         ` Gábor Stefanik
2009-02-23 23:33                           ` Luis R. Rodriguez

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=499C8DD2.7000800@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=mcgrof@gmail.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).