From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: linville@tuxdriver.com, johannes@sipsolutions.net,
marcel@holtmann.org, kalle.valo@nokia.com, kyle@mcmartin.ca,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/5] cfg80211: enable active-scan / beaconing on Ch 1-11 for world regdom
Date: Fri, 20 Feb 2009 12:08:53 -0800 [thread overview]
Message-ID: <43e72e890902201208i1ef39d8ey5624a29168c426b8@mail.gmail.com> (raw)
In-Reply-To: <69e28c910902201159y1ba18657qdb1517892e6fe352@mail.gmail.com>
On Fri, Feb 20, 2009 at 11:59 AM, G=C3=A1bor Stefanik
<netrolller.3d@gmail.com> wrote:
> On Fri, Feb 20, 2009 at 7:04 AM, Luis R. Rodriguez
> <lrodriguez@atheros.com> wrote:
>> This enables active scan and beaconing on Channels 1 through 11
>> on the static world regulatory domain.
>>
>> Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
>> ---
>> net/wireless/reg.c | 5 ++---
>> 1 files changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
>> index 605299f..8f64575 100644
>> --- a/net/wireless/reg.c
>> +++ b/net/wireless/reg.c
>> @@ -76,9 +76,8 @@ static const struct ieee80211_regdomain world_regd=
om =3D {
>> .n_reg_rules =3D 1,
>> .alpha2 =3D "00",
>> .reg_rules =3D {
>> - REG_RULE(2412-10, 2462+10, 40, 6, 20,
>> - NL80211_RRF_PASSIVE_SCAN |
>> - NL80211_RRF_NO_IBSS),
>> + /* IEEE 802.11b/g, channels 1..11 */
>> + REG_RULE(2412-10, 2462+10, 40, 6, 20, 0),
>> }
>> };
>>
>> --
>> 1.6.0.3
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wire=
less" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> Are you sure there is no area of the world where the allowed range is
> stricter than b/g 1-11?
> Otherwise I am inclined to NACK this.
That is the value of our world regulatory domain in wireless-regdb and
that itself is the product of the intersection of all currently known
regulatory domains, so yes, hence the patch.
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
next prev parent reply other threads:[~2009-02-20 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:04 [PATCH 0/5] cfg80211: enhance world roaming Luis R. Rodriguez
2009-02-20 6:04 ` [PATCH 1/5] cfg80211: enable active-scan / beaconing on Ch 1-11 for world regdom Luis R. Rodriguez
2009-02-20 19:59 ` Gábor Stefanik
2009-02-20 20:08 ` Luis R. Rodriguez [this message]
2009-02-20 6:04 ` [PATCH 2/5] cfg80211: enable 5 GHz world roaming channels Luis R. Rodriguez
2009-02-20 6:04 ` [PATCH 3/5] cfg80211: Add AP beacon regulatory hints Luis R. Rodriguez
2009-02-20 17:06 ` Johannes Berg
2009-02-20 20:34 ` Luis R. Rodriguez
2009-02-20 6:04 ` [PATCH 4/5] ath9k: follow beacon hints on reg_notifier when world roaming Luis R. Rodriguez
2009-02-20 6:04 ` [PATCH 5/5] cfg80211: default OLD_REG to n Luis R. Rodriguez
2009-02-20 6:08 ` [PATCH 0/5] cfg80211: enhance world roaming 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=43e72e890902201208i1ef39d8ey5624a29168c426b8@mail.gmail.com \
--to=lrodriguez@atheros.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@nokia.com \
--cc=kyle@mcmartin.ca \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=marcel@holtmann.org \
--cc=netrolller.3d@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