Linux wireless drivers development
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Phattanon Duangdara <sfalpha@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] wireless-regdb: TH gets 5 GHz enabled as of new regulatory rules
Date: Wed, 5 Aug 2009 14:17:26 -0400	[thread overview]
Message-ID: <20090805181726.GC20338@tuxdriver.com> (raw)
In-Reply-To: <f7de31c0907292246h6002e9bdod9691c2f24456017@mail.gmail.com>

On Thu, Jul 30, 2009 at 12:46:29PM +0700, Phattanon Duangdara wrote:
> On Wed, Jul 29, 2009 at 10:18 PM, Luis R.
> Rodriguez<lrodriguez@atheros.com> wrote:
> > Note: this e-mail is in a public mailing list.
> >
> > Adding Michael and David. Michael, I'd appreciate your review on this,
> > if possible.
> >
> > Phattanon, thanks for your review of the TH document and sharing it
> > with us. Please see my reply inline below.
> >
> > On Wed, Jul 29, 2009 at 3:13 AM, Phattanon Duangdara<sfalpha@gmail.com> wrote:
> >> I corrected redgb from my knowledge.
> >
> > Did you see my patch? I corrected TH to be:
> >
> > 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)
> >
> >> For 5150-5350 is for Indoor Use Only.
> >> Most of the regulartory
> >
> > What do you mean by that? Do you mean that the document refers to FCC
> > and ETSI/ITU standard for regulatory purposes for some items?
> >
> >> refer _either_ FCC or ETSI/ITU standard, so I
> >> guess that from the document 40MHz can also be used (same as US)
> >> because TH regulatory mostly cover all bandwidth on 40MHz.
> >
> > Are you saying the Thailand document refers to FCC for max allowed
> > bandwidth spacing and therefore US max bandwidth spacing should be
> > used (ie allow 40 MHz width channels)?
> 
> I am not sure about this. But if equipment that comply with FCC
> standard allow to use 40MHz, I think we can because, for example
> Translated rule for 2.4GHz says

<snip>

So, is the patch from Luis wrong?  If so, what is the correct patch?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.
			¡Viva Honduras Libre!

  reply	other threads:[~2009-08-05 18:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 17:51 [PATCH] wireless-regdb: TH gets 5 GHz enabled as of new regulatory rules Luis R. Rodriguez
2009-07-29 10:13 ` Phattanon Duangdara
2009-07-29 15:18   ` Luis R. Rodriguez
     [not found]     ` <f7de31c0907292242s7c41daefr6ca7b3423180d005@mail.gmail.com>
2009-07-30  5:46       ` Phattanon Duangdara
2009-08-05 18:17         ` John W. Linville [this message]
2009-08-05 18:58           ` Luis R. Rodriguez

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=20090805181726.GC20338@tuxdriver.com \
    --to=linville@tuxdriver.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