Message-ID: <499C8DD2.7000800@lwfinger.net> (sfid-20090218_233844_314855_B7D1AED6)
Date: Wed, 18 Feb 2009 16:38:10 -0600
From: Larry Finger <Larry.Finger@lwfinger.net>
MIME-Version: 1.0
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
References: <499C7DC0.4040608@lwfinger.net> <1234992712.4023.60.camel@johannes.local> <20090218220531.GD4246@tesla>
In-Reply-To: <20090218220531.GD4246@tesla>
Content-Type: text/plain; charset=ISO-8859-1
Sender: linux-wireless-owner@vger.kernel.org

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