From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from www.clear-code.com ([219.94.198.64]:47100 "EHLO mail.clear-code.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757860Ab0FOO0L convert rfc822-to-8bit (ORCPT ); Tue, 15 Jun 2010 10:26:11 -0400 Date: Tue, 15 Jun 2010 23:25:58 +0900 (JST) Message-Id: <20100615.232558.867740727379709943.kou@clear-code.com> To: mcgrof@gmail.com Cc: Stephen.Chen@atheros.com, David.Quan@atheros.com, linux-wireless@vger.kernel.org, Michael.Green@atheros.com Subject: Re: [PATCH] zd1211rw: ignore unknown regulatory domain. From: Kouhei Sutou In-Reply-To: References: <20100613.145200.1459063883179763823.kou@clear-code.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi, In "Re: [PATCH] zd1211rw: ignore unknown regulatory domain." on Sun, 13 Jun 2010 13:23:20 -0700, "Luis R. Rodriguez" wrote: >> I'm using PLANEX GW-US54GXS (2019:5303) and it works with >> the attached patch. Could you consider to merge the attached >> patch? >> >> Problem: GW-US54GXS uses zd1211rw but zd1211rw doesn't have >> a regulatory domain reported by GW-US54GXS (0x49). >> >> Solutions: >> >>  (1) add a new regulatory domain (0x49). Here is a patch to >>      use the approach: > > Stephen, David, does 0x49 map to JP for zd1211 ? Are there other ones? > Here is our list so far: ... > Kouhei, if no regulatory domain is found, instead we should world > roam, we cannot allow letting the user change regulatory domains at > their whim. We can, however let them choose one to help compliance, > but you can only help compliance once you know your actual regulatory > domain. Luis, thanks for your input. It seems that we can't use GW-US54GXS until 0x49 regulatory domain is registered to zd1211rw. Is it right? If it is right, what I can do for GW-US54GXS? Should I wait a response from Stephen and/or David? Thanks, -- kou