Subject: Re: [PATCH] wireless: fix regression caused by regulatory config
	option
From: Marcel Holtmann <holtmann@linux.intel.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "John W. Linville" <linville@tuxdriver.com>, torvalds@linux-foundation.org,
       netdev@vger.kernel.org, linux-kernel@vger.kernel.org, rjw@sisk.pl,
       rodriguez@atheros.com, johannes@sipsolutions.net
In-Reply-To: <20081026131818.7517c103@infradead.org>
References: <20081026103024.2712ddc9@infradead.org>
	 <20081026200939.GC12648@tuxdriver.com>
	 <20081026131818.7517c103@infradead.org>
Content-Type: text/plain
Date: Sun, 26 Oct 2008 23:12:37 +0100
Message-Id: <1225059157.7157.3.camel@californication>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1338
Lines: 38

Hi Arjan,

> > > Change the default to "y" and also adjust the config text a little
> > > to reflect this.
> > 
> > Is it common practice to have compatibility options default to
> > "y"?  I'm not saying it shouldn't be, just wondering if it has been
> > traditionally?
> 
> yes
> 
> default should be "keep working as before"
> 
> it's not always nice, especially if you're trying to get rid of some
> nasty stuff, but think of it this way: you should be able to use a
> new kernel on an existing distro, at least for a reasonable type of
> distro (eg something shipped in, say, the last 2 years). In this case:
> even Fedora 10 is not likely to work!

I think with the new patches from Johannes to make the regulatory
interaction easier for hardware that has hardware/EEPROM based
regulatory enforcement like our wireless cards, it should be all good.

That seems to be 2.6.20 stuff and then it seems to be safe to remove the
WIRELESS_OLD_REGULATORY option and it would still work with old
userspace (or missing crda/iw) in cases the hardware does regulatory
enforcement.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/