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: Fri, 24 Oct 2008 04:19:07 -0700 [thread overview]
Message-ID: <20081024111907.GC5951@tesla> (raw)
In-Reply-To: <49018B87.8070908@free.fr>
On Fri, Oct 24, 2008 at 01:47:03AM -0700, Benoit PAPILLAULT wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Luis R. Rodriguez a =E9crit :
> > On Wed, Oct 22, 2008 at 10:31:13PM -0700, Benoit PAPILLAULT wrote:
> >>> 2483.5 - 2454 =3D 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. Mayb=
e 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.
>=20
> The whole band is still 2412-2483.5MHz in both cases (indoor/outdoor)=
,
> this is just that different TX power rules apply for frequencies belo=
w
> 2454 MHz and above when used outdoor.
>=20
> To me, it's valid to have a 40MHz channel centered at 2462 MHz coveri=
ng
> the range [2442, 2482] MHz. When used outdoor, it will be limited to =
10
> dBm on the whole range.
This is an interesting case... so right now we apply a reg rule to
a channel upon register or when a regulatory domain changes. We do
this in handle_channel(). This calls freq_reg_info() and one parameter
we can pass there is the max_bandwidth we know we want or 0 if we have
no requirement. We use 0 on max_bandwidth right now as we haven't added
code for checking max bandwidth yet in mac80211, I think we can add
desired tx power here as well and it'll then be able to pick up the
correct rule. However this does require adding code to reg.c. and
maybe mac80211. We'll have to keep this in mind and add it, but
the reg rule for 2454 - 2483.5 should still not have 40 MHz for max
bandwidth as only 29.5 MHz fits in it.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-24 18:19 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
2008-10-24 8:47 ` Benoit PAPILLAULT
2008-10-24 11:19 ` Luis R. Rodriguez [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=20081024111907.GC5951@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 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).