From: "Arend van Spriel" <arend@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: "Seth Forshee" <seth.forshee@canonical.com>,
linux-wireless@vger.kernel.org,
"Kalle Valo" <kvalo@qca.qualcomm.com>
Subject: Re: [RFC PATCH 0/8] brcm80211: smac: rework regulatory support
Date: Sat, 26 May 2012 08:38:31 +0200 [thread overview]
Message-ID: <4FC07A67.6010704@broadcom.com> (raw)
In-Reply-To: <CAB=NE6XsTtJvmJDVa2toJCsjn1fxH+5cqJ8xkaquNhHcHDgh2A@mail.gmail.com>
On 05/26/2012 12:51 AM, Luis R. Rodriguez wrote:
>> It took a while. There were some discussions and we agreed that your
>> > changes establish a better integration with the regulatory framework.
>> > There are some concerns about the content of the crda database, but that
>> > is another thing outside the scope of your patches.
> BTW if you would like to address anything please let me know. If you'd like
> to review things in private too that's fine, just let me know. I
> should say that the staging area for the next generation regulatory
> code is being done through the regulatory simulator:
>
> git://github.com/mcgrof/regsim.git
Thanks, Luis. I mainly focused on the crda database and it has a
relation freqs<->pwr_limit. In our regulatory code we make a distinction
between 11n and abg as we believe that is necessary. Another example
would be 20MHz transmission in 40MHz channel. Maybe that is taken into
account in crda code, but I did not have a close look at it yet.
I will have a look at the regsim repository and follow up on that.
> Arend, in the future please trim all hunks that are not relevant to
> your replies, that makes review easier.
Will do.
Gr. AvS
next prev parent reply other threads:[~2012-05-26 6:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 20:17 [RFC PATCH 0/8] brcm80211: smac: rework regulatory support Seth Forshee
2012-04-16 20:17 ` [RFC PATCH 1/8] brcm80211: smac: don't set up tx power limits during initialization Seth Forshee
2012-05-25 22:32 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 2/8] brcm80211: smac: always set channel specified by mac80211 Seth Forshee
2012-05-25 22:32 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 3/8] brcm80211: smac: clean up channel.c Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-05-26 17:17 ` Seth Forshee
2012-05-27 11:51 ` Arend van Spriel
2012-05-27 11:53 ` Arend van Spriel
2012-05-29 12:46 ` Seth Forshee
2012-05-29 13:03 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 4/8] brcm80211: smac: inform mac80211 of the X2 regulatory domain Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-05-26 17:18 ` Seth Forshee
2012-05-27 12:17 ` Arend van Spriel
2012-05-29 13:12 ` Seth Forshee
2012-05-29 16:44 ` Arend van Spriel
2012-05-31 14:46 ` Seth Forshee
2012-05-31 17:49 ` Arend van Spriel
2012-06-07 18:18 ` Luis R. Rodriguez
2012-04-16 20:17 ` [RFC PATCH 5/8] brcm80211: smac: enable/disable radio on regulatory updates Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-05-26 17:18 ` Seth Forshee
2012-05-27 12:18 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 6/8] brcm80211: smac: use mac80211 channel data for tx power limits Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 7/8] brcm80211: smac: don't validate channels against internal regulatory data Seth Forshee
2012-05-25 22:33 ` Arend van Spriel
2012-04-16 20:17 ` [RFC PATCH 8/8] brcm80211: smac: use current regulatory domain when checking whether OFDM is allowed Seth Forshee
2012-05-25 22:34 ` Arend van Spriel
2012-04-16 20:42 ` [RFC PATCH 0/8] brcm80211: smac: rework regulatory support Arend van Spriel
2012-04-16 20:53 ` Seth Forshee
2012-04-19 19:31 ` Arend van Spriel
2012-04-19 19:46 ` Seth Forshee
2012-04-30 17:12 ` Seth Forshee
2012-05-01 12:13 ` Arend van Spriel
2012-05-01 16:12 ` Seth Forshee
2012-05-25 22:31 ` Arend van Spriel
2012-05-25 22:51 ` Luis R. Rodriguez
2012-05-26 6:38 ` Arend van Spriel [this message]
2012-05-26 7:19 ` Luis R. Rodriguez
2012-05-26 17:17 ` Seth Forshee
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=4FC07A67.6010704@broadcom.com \
--to=arend@broadcom.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=seth.forshee@canonical.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.