From: Seth Forshee <seth.forshee@canonical.com>
To: Arend van Spriel <arend@broadcom.com>, linux-wireless@vger.kernel.org
Cc: Brett Rudley <brudley@broadcom.com>,
Roland Vossen <rvossen@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
Kan Yan <kanyan@broadcom.com>,
Pieter-Paul Giesberts <pieterpg@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH v2 0/9] brcm80211: smac: rework regulatory support
Date: Tue, 12 Jun 2012 11:56:42 -0500 [thread overview]
Message-ID: <20120612165642.GG11723@thinkpad-t410> (raw)
In-Reply-To: <1338906849-26135-1-git-send-email-seth.forshee@canonical.com>
On Tue, Jun 05, 2012 at 09:34:00AM -0500, Seth Forshee wrote:
> brcmsmac has its own internal regulatory implementation which attempts
> to enforce a Broadcom defined domain named X2. This code has no
> integration with mac80211 regulatory other than supplying regulatory
> hints, and thus each implementation operates independently of the other,
> enforcing conflicting sets of rules.
>
> This series of patches converts brcmsmac to relying on the mac80211
> regulatory implementation. The X2 domain is registered with mac80211,
> and brcmsmac is converted to using the constraints from mac80211 for
> hardware configuration. Much code is removed in the process :)
>
> There is one holdover from the old regulatory implementation. The MIMO
> tx power limits for brcmsmac are still being configured based on
> internal data for the X2 domain. Arend is trying to find out how these
> need to be handled, but this can be changed at a later time.
>
> Changes since version 1:
>
> - Dropped patch to remove support for DFS channels
> - Added back application of flags for radar channels on regulatory
> updates from RFC patches, with minor simplifications
> - Removed unneeded NULL pointer check from regulatory notifier callback
>
> Thanks,
> Seth
Any more issues with this round that need to be addressed? If so I'd
like to get to work on them soon, so that we can hopefully get this
stuff in for 3.6.
Thanks,
Seth
next prev parent reply other threads:[~2012-06-12 16:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 14:34 [PATCH v2 0/9] brcm80211: smac: rework regulatory support Seth Forshee
2012-06-05 14:34 ` [PATCH v2 1/9] brcm80211: smac: don't set up tx power limits during initialization Seth Forshee
2012-06-05 14:34 ` [PATCH v2 2/9] brcm80211: smac: always set channel specified by mac80211 Seth Forshee
2012-06-05 14:34 ` [PATCH v2 3/9] brcm80211: smac: remove unused code for 40MHz channels Seth Forshee
2012-06-13 15:37 ` Seth Forshee
2012-06-13 15:49 ` Arend van Spriel
2012-06-05 14:34 ` [PATCH v2 4/9] brcm80211: smac: clean up channel.c Seth Forshee
2012-06-05 14:34 ` [PATCH v2 5/9] brcm80211: smac: inform mac80211 of the X2 regulatory domain Seth Forshee
2012-06-05 14:34 ` [PATCH v2 6/9] brcm80211: smac: enable/disable radio on regulatory updates Seth Forshee
2012-06-13 9:28 ` Arend van Spriel
2012-06-13 13:43 ` Seth Forshee
2012-06-13 14:26 ` Arend van Spriel
2012-06-05 14:34 ` [PATCH v2 7/9] brcm80211: smac: use mac80211 channel data for tx power limits Seth Forshee
2012-06-13 9:39 ` Arend van Spriel
2012-06-13 13:46 ` Seth Forshee
2012-06-13 14:27 ` Arend van Spriel
2012-06-05 14:34 ` [PATCH v2 8/9] brcm80211: smac: don't validate channels against internal regulatory data Seth Forshee
2012-06-05 14:34 ` [PATCH v2 9/9] brcm80211: smac: use current regulatory domain when checking whether OFDM is allowed Seth Forshee
2012-06-12 16:56 ` Seth Forshee [this message]
2012-06-13 9:43 ` [PATCH v2 0/9] brcm80211: smac: rework regulatory support Arend van Spriel
2012-06-13 13:50 ` Seth Forshee
2012-06-16 11:57 ` Arend van Spriel
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=20120612165642.GG11723@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=kanyan@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=pieterpg@broadcom.com \
--cc=rvossen@broadcom.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).