From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"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 7/9] brcm80211: smac: use mac80211 channel data for tx power limits
Date: Wed, 13 Jun 2012 16:27:29 +0200 [thread overview]
Message-ID: <4FD8A351.30008@broadcom.com> (raw)
In-Reply-To: <20120613134651.GB3490@thinkpad-t410>
On 06/13/2012 03:46 PM, Seth Forshee wrote:
> On Wed, Jun 13, 2012 at 11:39:47AM +0200, Arend van Spriel wrote:
>> On 06/05/2012 04:34 PM, Seth Forshee wrote:
>>> Currently the limits from the internal X2 domain are used, regardless
>>> of what regulatory rules are in effect. Instead use the power limits set
>>> by the higher-level regulatory support.
>>>
>>> The rules for the MIMO power limits are still always derived from the
>>> world domain. Guidance from Broadcom is needed on how these limits
>>> should be determined for other regulatory domains.
>>
>> Have not got definite answer yet. Luis indicated that Qualcomm/Atheros
>> had similar construct, but that is was not really needed and could be
>> derived. I will have to follow up on it in a separate patch.
>
> Thanks, that confirms my understanding of the state of things from
> previous discussion.
>
> Would you like me to modify that statement in some way? Or was your
> comment purely informational? Reading it again, I probably will at least
> add a comment to indicate that the state of things is workable for now
> and will be improved later.
>
My comment was informational, but feel free to add a comment.
Gr. AvS
next prev parent reply other threads:[~2012-06-13 14:27 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 [this message]
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 ` [PATCH v2 0/9] brcm80211: smac: rework regulatory support Seth Forshee
2012-06-13 9:43 ` 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=4FD8A351.30008@broadcom.com \
--to=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 \
--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.