Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Tom Sharples" <tsharples@qorvus.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>,
	"David Acker" <dacker@roinet.com>
Cc: "linux-wireless" <linux-wireless@vger.kernel.org>,
	<madwifi-users@lists.sourceforge.net>,
	"Andrey Yurovsky" <andrey@cozybit.com>,
	<madwifi-devel@lists.sourceforge.net>
Subject: Re: [Madwifi-devel] Survey: What are you using MadWifi for, and why?
Date: Tue, 17 Nov 2009 15:39:14 -0800	[thread overview]
Message-ID: <7C9BF2FB3F6D47238EB6BC9B4441A996@qlaptop2> (raw)
In-Reply-To: 43e72e890911171439q74f30bc2t3e6f4ada19a85594@mail.gmail.com


>
>> There are several miniPCI
>> based radios that require half or quarter width channels on some 
>> channels.
>
> That *require* this?
>
>> For example, the Ubiquiti XR7 requires quarter width channels on two of 
>> its
>> four available channels.
>
> Regulatory wise? What's the restriction based on?
>
>> The XR9 requires half width channels on two if its
>> four available channels.
>
> Same here, what's the restriction based on?
>
On 900 and the 4.9 Ghz public safety bands, the half or quarter channels are 
required if you want to:

(a) Support multiple non-overlapping links within the legally allocated 
bandwidth. For example, within 900 Mhz there is only 25 Mhz total available, 
and only two 20-mhz channels defined (which, of course, overlap) so really 
you've only got one. With 5 Mhz channels, you can operate legally near the 
edge of the band without interfering with other 900 Mhz links, or 
transmitting outside of the FCC allocated band.

(b) Operate legally and efficiently in the 4.9 Ghz public-safety band. The 
upper and lower three channels defined by the FCC are 5Mhz and 10Mhz. 20 Mhz 
operation there would violate the allocated band edges.

(b) Be compatible with other company's products that use these channels, 
e.g. Proxim, Cisco, Ubiquiti, etc.

On 2.4 and 5.8 half and quarter aren't a legal requirement, but they 
certainly are necessary for efficient operation!

Tom S. 


  reply	other threads:[~2009-11-17 23:39 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 [this message]
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
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=7C9BF2FB3F6D47238EB6BC9B4441A996@qlaptop2 \
    --to=tsharples@qorvus.com \
    --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