Return-path: Received: from fg-out-1718.google.com ([72.14.220.159]:55663 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752898AbZBTVHI convert rfc822-to-8bit (ORCPT ); Fri, 20 Feb 2009 16:07:08 -0500 Received: by fg-out-1718.google.com with SMTP id 16so2090791fgg.17 for ; Fri, 20 Feb 2009 13:07:06 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <43e72e890902201233w95b4aaew1fa0bbf06196d74f@mail.gmail.com> References: <499C7DC0.4040608@lwfinger.net> <1234992712.4023.60.camel@johannes.local> <20090218220531.GD4246@tesla> <499C8DD2.7000800@lwfinger.net> <20090218224833.GB28733@bombadil.infradead.org> <69e28c910902201145h6d9fa472rc81da56ffce16dc0@mail.gmail.com> <43e72e890902201233w95b4aaew1fa0bbf06196d74f@mail.gmail.com> Date: Fri, 20 Feb 2009 22:07:05 +0100 Message-ID: <69e28c910902201307i398b4a89na4ce0205d66ee921@mail.gmail.com> (sfid-20090220_220716_037104_FDE47688) Subject: Re: ieee80211_regdom module parameter for cfg80211 From: =?ISO-8859-1?Q?G=E1bor_Stefanik?= To: "Luis R. Rodriguez" Cc: "Luis R. Rodriguez" , Larry Finger , Johannes Berg , wireless , John Linville Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Fri, Feb 20, 2009 at 9:33 PM, Luis R. Rodriguez w= rote: > On Fri, Feb 20, 2009 at 11:45 AM, G=E1bor Stefanik > wrote: >> On Wed, Feb 18, 2009 at 11:48 PM, Luis R. Rodriguez >> wrote: >>> On Wed, Feb 18, 2009 at 04:38:10PM -0600, Larry Finger wrote: >>>> 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 u= ser set their >>>> >>> regulatory domain by creating the file /etc/modprobe.d/cfg8021= 1 with the >>>> >>> contents "ieee80211_regdom=3DUS". >>>> >>> >>>> >>> 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 crd= a 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_RE= G. Static regdoms >>>> > for US, JP and EU fall into that and so does the module paramete= r. I believe >>>> > it is silly to keep the module parameter around as we already ha= ve userspace >>>> > 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 >>>> are those that upgrade their distro. >>> >>> Yeah, if they disable OLD_REG -- but I am curious which distributio= ns are using this >>> themselves as well. Would you happen to know ? Or are you mostly se= eing just users >>> 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 >> easy way for users to upgrade kernels without a full distro upgrade = - >> modparams have a much simpler syntax than init scripts. If we keep t= he >> 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