linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: madwifi-users@lists.sourceforge.net,
	linux-wireless <linux-wireless@vger.kernel.org>,
	madwifi-devel@lists.sourceforge.net,
	David Acker <dacker@roinet.com>,
	Andrey Yurovsky <andrey@cozybit.com>
Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why?
Date: Wed, 18 Nov 2009 18:12:33 -0500	[thread overview]
Message-ID: <1258585953.9914.5.camel@mj> (raw)
In-Reply-To: <43e72e890911181408r43dadf7av277b255eb9007481@mail.gmail.com>

On Wed, 2009-11-18 at 14:08 -0800, Luis R. Rodriguez wrote:

> So for now countries either take the FCC, are part of a larger group
> like in Europe or are a head ache to deal with due to historical
> changes on regulatory rules (Japan). So far I've seen rules set for
> bands and with max EIRP and antenna gain. Sometimes you have quirky
> rules for antenna gain like in the US for the 3:1 rule (but we don't
> yet allow you to modify your antenna on linux and specific your new
> dbi antenna gain, and this actually is assumed won't change on the
> client side).
> 
> For width I'm told some countries do not allow HT40 and that this
> should change in the future.
> 
> I haven't seen rules for finer level of control which is why I said I
> we should not need to change anything. Right now  I've only have heard
> of countries sometimes disallowing HT40, but that's it.
> 
> Are you aware of any regulatory rules which prohibit narrower
> channels? It just seems odd.

No, I'm not aware of such limitations.  OK, you are not aware of such
limitations either, then perhaps we can go ahead with the narrow
channels.

-- 
Regards,
Pavel Roskin

  parent reply	other threads:[~2009-11-18 23:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2205.95.222.251.107.1258282369.squirrel@webmail.otaku42.de>
2009-11-17  1:01 ` [Madwifi-devel] Survey: What are you using MadWifi for, and why? Luis R. Rodriguez
2009-11-17 14:05   ` John W. Linville
2009-11-17 22:08     ` Marcel Holtmann
2009-11-17 16:04   ` Michael Renzmann
2009-11-17 16:38     ` Luis R. Rodriguez
2009-11-17 17:51       ` Tom Sharples
2009-11-17 18:05         ` Luis R. Rodriguez
2009-11-17 21:51       ` Bob Copeland
2009-11-17 23:23         ` Pat Erley
2009-11-18  7:23       ` Michael Renzmann
2009-11-17 17:40   ` David Acker
2009-11-17 20:57     ` Andrey Yurovsky
2009-11-17 21:37       ` Luis R. Rodriguez
2009-11-17 21:44         ` David Acker
2009-11-17 21:45           ` Luis R. Rodriguez
2009-11-17 21:53             ` David Acker
2009-11-17 22:04               ` Luis R. Rodriguez
2009-11-17 22:28                 ` David Acker
2009-11-17 22:39                   ` Luis R. Rodriguez
2009-11-17 23:39                     ` Tom Sharples
2009-11-17 23:44                       ` Luis R. Rodriguez
2009-11-17 22:54                   ` Jouni Malinen
2009-11-17 23:12                     ` Luis R. Rodriguez
2009-11-18 21:58                       ` Pavel Roskin
2009-11-18 22:08                         ` Luis R. Rodriguez
2009-11-18 23:05                           ` Jouni Malinen
2009-11-19  0:21                             ` Luis R. Rodriguez
2009-11-18 23:12                           ` Pavel Roskin [this message]
2009-11-19  0:05                             ` Tom Sharples
2009-11-17 22:06               ` Marcel Holtmann
2009-11-17 22:32                 ` David Acker
2009-11-17 23:22               ` Felix Fietkau
2009-11-18 15:35                 ` David Acker

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=1258585953.9914.5.camel@mj \
    --to=proski@gnu.org \
    --cc=andrey@cozybit.com \
    --cc=dacker@roinet.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=madwifi-users@lists.sourceforge.net \
    --cc=mcgrof@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;
as well as URLs for NNTP newsgroup(s).