linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Kouhei Sutou <kou@clear-code.com>,
	Stephen Chen <Stephen.Chen@atheros.com>,
	David Quan <David.Quan@atheros.com>
Cc: linux-wireless@vger.kernel.org,
	Michael Green <Michael.Green@atheros.com>
Subject: Re: [PATCH] zd1211rw: ignore unknown regulatory domain.
Date: Sun, 13 Jun 2010 13:23:20 -0700	[thread overview]
Message-ID: <AANLkTinEMAQu33Tlv81-Cdx9fLZK-a-7uJlbAo7te2_w@mail.gmail.com> (raw)
In-Reply-To: <20100613.145200.1459063883179763823.kou@clear-code.com>

Note: this e-mail is on a public mailing list!

On Sat, Jun 12, 2010 at 10:52 PM, Kouhei Sutou <kou@clear-code.com> wrote:
> Hi,
>
> 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:

#define ZD_REGDOMAIN_FCC        0x10
#define ZD_REGDOMAIN_IC         0x20
#define ZD_REGDOMAIN_ETSI       0x30
#define ZD_REGDOMAIN_SPAIN      0x31
#define ZD_REGDOMAIN_FRANCE     0x32
#define ZD_REGDOMAIN_JAPAN_ADD  0x40
#define ZD_REGDOMAIN_JAPAN      0x41

This is what they map to:

static struct zd_reg_alpha2_map reg_alpha2_map[] = {
        { ZD_REGDOMAIN_FCC, "US" },
        { ZD_REGDOMAIN_IC, "CA" },
        { ZD_REGDOMAIN_ETSI, "DE" }, /* Generic ETSI, use most restrictive */
        { ZD_REGDOMAIN_JAPAN, "JP" },
        { ZD_REGDOMAIN_JAPAN_ADD, "JP" },
        { ZD_REGDOMAIN_SPAIN, "ES" },
        { ZD_REGDOMAIN_FRANCE, "FR" },
};

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

  reply	other threads:[~2010-06-13 20:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-13  5:52 [PATCH] zd1211rw: ignore unknown regulatory domain Kouhei Sutou
2010-06-13 20:23 ` Luis R. Rodriguez [this message]
2010-06-15 14:25   ` Kouhei Sutou
2010-06-15 15:22     ` Luis R. Rodriguez
2010-06-16 12:55       ` Kouhei Sutou
2010-06-16 13:44         ` John W. Linville
2010-06-16 15:02           ` Kouhei Sutou
2010-06-16 15:29             ` John W. Linville
2010-06-16 15:46               ` Luis R. Rodriguez
2010-06-15 17:40   ` Gábor Stefanik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinEMAQu33Tlv81-Cdx9fLZK-a-7uJlbAo7te2_w@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=David.Quan@atheros.com \
    --cc=Michael.Green@atheros.com \
    --cc=Stephen.Chen@atheros.com \
    --cc=kou@clear-code.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).