From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Benoit PAPILLAULT <benoit.papillault@free.fr>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [PATCH 4/5] crda: Updated regulatory information for France (FR)
Date: Thu, 23 Oct 2008 04:07:46 -0700 [thread overview]
Message-ID: <20081023110746.GA5979@tesla> (raw)
In-Reply-To: <49000C21.2010808@free.fr>
On Wed, Oct 22, 2008 at 10:31:13PM -0700, Benoit PAPILLAULT wrote:
> >> +# Data from http://www.arcep.fr/index.php?id=9272#12931
> >> +# Updated 2008-10-04
> >> +# 1W => 30dBm, 200mW => 23dBm, 100mW => 20dBm, 10mW => 10dBm
> >> +# TPC is needed for 5250-5350 and 5470-5725, which flag to use?
> >> country FR:
> >> - (2402 - 2482 @ 40), (N/A, 20)
> >> - (5170 - 5250 @ 40), (N/A, 20)
> >> - (5250 - 5330 @ 40), (N/A, 20), DFS
> >> - (5490 - 5710 @ 40), (N/A, 27), DFS
> >> + (2400 - 2454 @ 40), (N/A, 20)
> >> + (2454 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
> >
> > 2483.5 - 2454 = 29.5 so 29.5 should be the max bandwidth.
>
> Not exactly. The maximum power in this band depends on whether we are
> indoor or outdoor. If we are indoor, we are allowed to have 20dBm in the
> whole 2400 - 2454 MHz band and can still use 40MHz bandwidth. Maybe I
> should describe that different?
>
> (2412 - 2483.5 @ 40), (N/A, 20), NO-OUTDOOR
> (2412 - 2454 @ 40), (N/A, 20), NO-INDOOR
> (2454 - 2483.5 @ 40) (N/A, 10), NO-INDOOR
>
> In fact, this depends on the indoor/outdoor flags issue which can be
> resolved later.
But I wasn't speaking about power, I was speaking about channel
bandwidth. You cannot fit a 40 MHz channel into the freq range
2483.5 - 2454.
> >> + (2454 - 2483.5 @ 40), (N/A, 10), NO-INDOOR
> >
> > Same here.
> >
> >> + (5150 - 5250 @ 40), (N/A, 23), NO-OUTDOOR
> >> + (5250 - 5350 @ 40), (N/A, 23), NO-OUTDOOR, DFS, PASSIVE-SCAN
> >> + (5470 - 5725 @ 40), (N/A, 30), DFS, PASSIVE-SCAN
> >
> > Hm, actually so I had removed PASSIVE-SCAN from all entries
> > as I had determined that this was only used for DFS purposes.
> > As you can see in your case both have DFS so I'd leave only DFS.
> > So essentially we can get rid of these:
> >
> > RRF_PASSIVE_SCAN = 1<<7, /* passive scan is required */
> > RRF_NO_IBSS = 1<<8, /* IBSS is not allowed */
> >
> > What I noted was that PASSIVE-SCAN for example was only used for when
> > we don't have DFS in STA and NO_IBSS when we don't have DFS in IBSS.
> >
> > So we can just stick to DFS flag, unless you are aware of other
> > considerations for them. Thoughts?
>
> If it's documented that the DFS flag implies PASSIVE_SCAN, that's fine
> with me.
We'll have to add the docs, this is just what what I determined from my
own review on regulatory, with regulatory folks. I asked a "why" for
each flag.
Luis
next prev parent reply other threads:[~2008-10-23 18:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1223583376.git.benoit.papillault@free.fr>
2008-10-21 20:20 ` [PATCH 4/5] crda: Updated regulatory information for France (FR) Benoit PAPILLAULT
2008-10-21 21:27 ` Johannes Berg
2008-10-22 15:03 ` Luis R. Rodriguez
2008-10-22 22:23 ` Jean Tourrilhes
2008-10-23 5:16 ` Benoit PAPILLAULT
2008-10-23 5:31 ` Benoit PAPILLAULT
2008-10-23 11:07 ` Luis R. Rodriguez [this message]
2008-10-24 8:47 ` Benoit PAPILLAULT
2008-10-24 11:19 ` 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=20081023110746.GA5979@tesla \
--to=lrodriguez@atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--cc=benoit.papillault@free.fr \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.