On Wed, Feb 18, 2009 at 10:51 PM, Kalle Valo <kalle.valo@xxxxxx> wrote: > "Luis R. Rodriguez" <lrodriguez@xxxxxxxxxxx> writes: > >> Since we are not following the schedule to remove OLD_REG by 2.6.29 >> lets simply set it to default to n for 2.6.30 and schedule its >> removal for 2.6.31 > > [...] > >> config WIRELESS_OLD_REGULATORY >> bool "Old wireless static regulatory definitions" >> - default y >> + default n >> ---help--- >> This option enables the old static regulatory information >> and uses it within the new framework. This is available > > What does this mean in practise? If a user compiles the kernel with > the default settings, the wireless will work only if crda is > installed? No, it means you get the static world regdomain by default instead of the static US world regdomain by default. > If that's the case, this is way too early. All lazy people, like me, > will get very frustrated because of this. They don't want to make all > those hoops to install crda, they just want their wireless to work. > > For example, I still can't find crda from debian unstable. In my > opinion we need to wait _at least_ a year after it's available in all > distros, and only then we can make crda the default. Keep in mind OLD_REG still alows usage of CRDA, OLD_REG just means "3 static regdomains, ieee80211_regdom module parameter, and make the US static regdom the default". That's all. > Let's not make the same mistake the udev people did. That was a > disaster few years back, I suffered from it multiple times. > Fortunately things have calmed down now and I can safely update the > kernel. Whatever works. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
