On Wed, Feb 18, 2009 at 11:34:58PM +0100, G=E1bor Stefanik wrote:

On Wed, Feb 18, 2009 at 11:05 PM, Luis R. Rodriguez
[off-list ref] wrote:

quoted

On Wed, Feb 18, 2009 at 01:31:52PM -0800, Johannes Berg wrote:

quoted

On Wed, 2009-02-18 at 15:29 -0600, Larry Finger wrote:

quoted

On at least one forum, I have seen the recommendation that a use=

r set their

quoted

quoted

quoted

regulatory domain by creating the file /etc/modprobe.d/cfg80211 =

with the

quoted

quoted

quoted

contents "ieee80211_regdom=3DUS".

That works as long as CONFIG_WIRELESS_OLD_REGULATORY is set in t=

heir .config,

quoted

quoted

quoted

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 mi=

ght not make any

quoted

quoted

quoted

sense, but it surely shouldn't kill wireless.

I actually see no reason to not just /honour/ it by calling crda w=

ith

quoted

quoted

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

quoted

for US, JP and EU fall into that and so does the module parameter. =

I believe

quoted

it is silly to keep the module parameter around as we already have =

userspace

quoted

APIs to let users set this.

=20
Keeping the module parameter as a way to set the initial regdomain is
helpful for users who upgrade the kernel of an older distro.

This makes sense, but what distributions are using this module paramete=
r?
As far as I can tell its only users using it.

And if there are distributions using it -- can we not expect them to st=
op
using it by they disable OLD_REG?

Adding a
line to /etc/modprobe.d/options would be a much easier way of setting
the right regdomain right during bootup than having to edit the init
scripts

Using init scripts is just one way of doing this, its not the only way.
Userspace can use user-configuration settings through wpa_supplicant,
hostapd, GPS devices can also provide hints, say through the usage of
GeoClue. That's really a lot neater than a module parameter or an init
script.

and it is also something that CRDA's "make install" could do
automagically (like "make install regdom=3DHU").

I'd rather not make that a practice provided we want to phase out OLD_R=
EG
and we want userspace to use nl80211 for this.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html