netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>,
	netdev@vger.kernel.org, Faidon Liambotis <faidon@cube.gr>,
	Rick Jones <rick.jones2@hp.com>,
	Ulrich Kunitz <kune@deine-taler.de>,
	Harald Welte <laforge@gnumonks.org>,
	Jouni Malinen <jkm@devicescape.com>,
	Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC] Proposed structure for Regulatory/Geographical Wireless database
Date: Sat, 06 May 2006 14:24:29 -0500	[thread overview]
Message-ID: <445CF7ED.9080705@lwfinger.net> (raw)
In-Reply-To: <200605062048.46390.mb@bu3sch.de>

Michael Buesch wrote:
> On Friday 05 May 2006 22:14, you wrote:
>> # Groups follow countries
>> #
>> Group 0         - Unspecified Country
>> #
>> # Band  Ch. Range       Ch. Spacing     Power   Flags
>           ^^^^^^^^^
> Aren't there countries around, where there are gaps in the
> allowed channel numbers? (Especially for 802.11a) So it would
> not be an allowed "range", but an allowed list of channels.
> 

Yes, but the gaps are only in 802.11a that I know about. If there is a gap, then I use a second line 
as was shown in the example for the standard EU specs. In most cases, other factors change as well. 
I initially was going to specify the allowed channels, but the tables got very long. This way is 
more compact.

Larry


      reply	other threads:[~2006-05-06 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 20:14 [RFC] Proposed structure for Regulatory/Geographical Wireless database Larry Finger
2006-05-05 21:08 ` Uli Kunitz
2006-05-05 21:23   ` Larry Finger
2006-05-06  5:07     ` Uli Kunitz
2006-05-05 21:10 ` Dan Williams
2006-05-05 21:52   ` Larry Finger
2006-05-06  1:31 ` Jouni Malinen
2006-05-07  2:02   ` Larry Finger
2006-05-06 18:48 ` Michael Buesch
2006-05-06 19:24   ` Larry Finger [this message]

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=445CF7ED.9080705@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=faidon@cube.gr \
    --cc=hch@infradead.org \
    --cc=jkm@devicescape.com \
    --cc=kune@deine-taler.de \
    --cc=laforge@gnumonks.org \
    --cc=mb@bu3sch.de \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.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).