Return-path: Received: from fg-out-1718.google.com ([72.14.220.158]:24505 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752248AbZKFMF5 (ORCPT ); Fri, 6 Nov 2009 07:05:57 -0500 Received: by fg-out-1718.google.com with SMTP id e12so226656fga.1 for ; Fri, 06 Nov 2009 04:06:01 -0800 (PST) Date: Fri, 06 Nov 2009 13:05:52 +0100 Message-ID: From: Holger Schurig To: Holger Schurig Cc: Jeffrey Baker , linux-wireless@vger.kernel.org, "Luis R. Rodriguez" Subject: Re: Getting random regulatory domains on boot-up with ath9k In-Reply-To: References: MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-wireless-owner@vger.kernel.org List-ID: Hmm, maybe it's not a bug after all. The card's eeprom just have a region, 0x37 is ETSI World. Now the kernel looks for the first country with this region and uses this for crda. There have been changes to drivers/net/wireless/ath/regd_common.h recently, so maybe on one kernel-version "DK" is the first ETSI World, on the next "AW" is the first and on some other again some different country. So it's just misleading, e.g. using first country with regdm 0x37: DK would probably a better dmesg output. If you however can reproduce that with the same kernel you always get different output after each reboot, then we have a bug here.