On Fri, Feb 20, 2009 at 9:33 PM, Luis R. Rodriguez [off-list ref] w=
rote:

On Fri, Feb 20, 2009 at 11:45 AM, G=E1bor Stefanik
[off-list ref] wrote:

quoted

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

quoted

On Wed, Feb 18, 2009 at 04:38:10PM -0600, Larry Finger wrote:

quoted

Luis R. Rodriguez 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 u=

ser set their

quoted

quoted

quoted

quoted

quoted

quoted

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

1 with the

quoted

quoted

quoted

quoted

quoted

quoted

contents "ieee80211_regdom=3DUS".

That works as long as CONFIG_WIRELESS_OLD_REGULATORY is set in=

 their .config,

quoted

quoted

quoted

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 =

might not make any

quoted

quoted

quoted

quoted

quoted

quoted

sense, but it surely shouldn't kill wireless.

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

a with

quoted

quoted

quoted

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

G. Static regdoms

quoted

quoted

quoted

quoted

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

r. I believe

quoted

quoted

quoted

quoted

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

ve userspace

quoted

quoted

quoted

quoted

APIs to let users set this.

I guess we leave it the way it is. At least the only people that w=

ill get caught

quoted

quoted

quoted

are those that upgrade their distro.

Yeah, if they disable OLD_REG -- but I am curious which distributio=

ns are using this

quoted

quoted

themselves as well. Would you happen to know ? Or are you mostly se=

eing just users

quoted

quoted

doing that themselves?

Yes, I was talking about users doing this, users who upgrade their
kernel without upgrading their distro. Keeping a modparam provides a=

n

quoted

easy way for users to upgrade kernels without a full distro upgrade =

-

quoted

modparams have a much simpler syntax than init scripts. If we keep t=

he

quoted

modparam as a way to control CRDA, this is what an user has to do to
upgrade:
1. Compile and install the new kernel. (Mostly straightforward, as
long as the user has a config and knows how to use make.)
2. Compile and install CRDA. (Straightforward.)
3. echo options cfg80211 ieee80211_regdom=3D"HU" >>
/etc/modprobe.d/options (Straightforward.)

Removing the modparam changes step 3 to:
3. Find the init scripts, and edit them to include "iw reg set HU",
making sure it happens early enough, caring about the syntax, taking
into account differences between distros, etc. Possibly includes
modifying the initramfs/initrd by hand in some odd distros. (Not
straightforward at all, requires knowledge of the distro's inner
workings, such as the init version used, e.g. sysvinit, bsdinit,
upstart, etc.)

It seems reasonable to keep the module parameter in case iw is not
installed but if users went through the trouble of installing crda ar=

e

we to not expect users to have iw also by 2.6.30?

=A0Luis

I am not talking about the case when iw is not installed - even if iw
is installed, it is much easier to edit the module options file than
the init scripts.

G=E1bor

--=20
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
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