Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: David Quan <David.Quan@atheros.com>
Cc: Phattanon Duangdara <sfalpha@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Michael Green <Michael.Green@atheros.com>
Subject: Re: Update for regulatory database on 5GHz band for Thailand (TH)
Date: Wed, 22 Jul 2009 09:41:39 -0700	[thread overview]
Message-ID: <43e72e890907220941j70f5ca98g5af9d9372eeef2e@mail.gmail.com> (raw)
In-Reply-To: <15B47C78534E094AA9A41F58FB8D74F30147BE67876F@SC1EXMB-MBCL.global.atheros.com>

On Wed, Jul 22, 2009 at 9:27 AM, David Quan<David.Quan@atheros.com> wrote:
> I am not sure what the question is here.
> Our windows driver already have 5G turn on for Thailand.
> Are you stating that it is not on the Linux Ath9K?

David, just a heads up, a public list is being CC'd here.

In the db.txt (from wireless-regdb) we currently have TH mapped as:

country TH:
        (2402 - 2482 @ 40), (N/A, 20)

This came from the regpair TH was mapped to, which does differ from
FCC3_WORLD. TH was mapped to NULL1_WORLD which explains the lack of 5
GHz on TH on db.txt.

> In Windows code, it is Thailand is mapped to FCC3_WORLD.

OK this needs to be updated and the regulatory database as well. Only
these countries map to FCC3_WORLD currently in ath.ko (the shared
module between ath5k, ath9k and ar9170):

	{CTRY_BRAZIL, FCC3_WORLD, "BR"},
	{CTRY_SOUTH_AFRICA, FCC3_WORLD, "ZA"},
	{CTRY_SRI_LANKA, FCC3_WORLD, "LK"},

To get TH to map to FCC3_WORLD we need a one line change to ath.ko
code and to the public db.txt to change to use the same regulatory
information as "BR", "ZA", and "LK":

country TH:
        (2402 - 2482 @ 20), (N/A, 20)
        (5170 - 5250 @ 20), (3, 17)
        (5250 - 5330 @ 20), (3, 20), DFS
        (5490 - 5710 @ 20), (3, 20), DFS
        (5735 - 5835 @ 20), (3, 30)

I'll send the respective patch if you ACK TH should map to the above.

  Luis

---

Below are BR, ZA and LK:

country BR:
        (2402 - 2482 @ 20), (N/A, 20)
        (5170 - 5250 @ 20), (3, 17)
        (5250 - 5330 @ 20), (3, 20), DFS
        (5490 - 5710 @ 20), (3, 20), DFS
        (5735 - 5835 @ 20), (3, 30)

country ZA:
        (2402 - 2482 @ 40), (N/A, 20)
        (5170 - 5250 @ 20), (3, 17)
        (5250 - 5330 @ 20), (3, 20), DFS
        (5490 - 5710 @ 20), (3, 20), DFS
        (5735 - 5835 @ 20), (3, 30)

country LK:
        (2402 - 2482 @ 40), (N/A, 20)
        (5170 - 5250 @ 20), (3, 17)
        (5250 - 5330 @ 20), (3, 20), DFS
        (5490 - 5710 @ 20), (3, 20), DFS
        (5735 - 5835 @ 20), (3, 30)

  reply	other threads:[~2009-07-22 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 13:07 Update for regulatory database on 5GHz band for Thailand (TH) Phattanon Duangdara
2009-07-22 13:19 ` John W. Linville
2009-07-22 14:04   ` Phattanon Duangdara
2009-07-22 16:16     ` Luis R. Rodriguez
2009-07-22 16:27       ` David Quan
2009-07-22 16:41         ` Luis R. Rodriguez [this message]
2009-07-23  7:57           ` Phattanon Duangdara
2009-07-23  8:31           ` Holger Schurig
2009-07-23  9:40             ` Johannes Berg
2009-07-22 13:33 ` Holger Schurig

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=43e72e890907220941j70f5ca98g5af9d9372eeef2e@mail.gmail.com \
    --to=mcgrof@gmail.com \
    --cc=David.Quan@atheros.com \
    --cc=Michael.Green@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sfalpha@gmail.com \
    /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