All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: "Luis R. Rodriguez" <rodrigue@qca.qualcomm.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCH 4/8] brcm80211: smac: inform mac80211 of the X2 regulatory domain
Date: Sun, 27 May 2012 14:17:03 +0200	[thread overview]
Message-ID: <4FC21B3F.6090903@broadcom.com> (raw)
In-Reply-To: <20120526171800.GC11759@ubuntu-mba>

On 05/26/2012 07:18 PM, Seth Forshee wrote:
> On Sat, May 26, 2012 at 12:33:15AM +0200, Arend van Spriel wrote:
>>> +#define BRCM_2GHZ_2412_2462	REG_RULE(2412-10, 2462+10, 40, 0, 19, 0)
>>> +#define BRCM_2GHZ_2467_2472	REG_RULE(2467-10, 2472+10, 20, 0, 19, \
>>> +					 NL80211_RRF_PASSIVE_SCAN | \
>>> +					 NL80211_RRF_NO_IBSS)
>>> +#define BRCM_2GHZ_2484		REG_RULE(2484-10, 2484+10, 40, 0, 19, \
>>> +					 NL80211_RRF_PASSIVE_SCAN | \
>>> +					 NL80211_RRF_NO_OFDM)
>>> +
>>
>> If channels 12 and 13 are 20MHz only, shouldn't channel 14 above
>> (2484MHz) be 20MHz as well?
> 
> Heh, good point. I'm trying to remember why I made 12 and 13 20MHz only
> though; maybe that's a mistake. Is there any reason why they couldn't
> all be 40MHz?

Not sure either. A number of countries have this rule so maybe it is
regulatory requirement.

>>
>> You can avoid this code if you/we do not add the channels to
>> wiphy->bands[IEEE80211_BAND_5GHZ]. The driver does not support DFS so we
>> better stay away from these channels, which was your original issue to
>> start this work if I recall correct :-( Sorry.
> 
> This is what originally got me looking at the brcmsmac regulatory
> support, so it would be disappointing if at the end these channels still
> aren't usable.

Hence me saying sorry.

> My understanding of DFS is pretty rudamentary. Could you explain what
> support is needed? I do see that mac80211 doesn't really support power
> measurement requests, but if we can at least stop transmission when
> radar is present couldn't we still operate on the channels?

The hardware would need to signal the driver that a radar has been detected.

> Luis, any insight you can offer on the subject would be appreciated.
> 
>>
>> can this be moved in brcms_c_channel_mgr_attach()?
> 
> Not without rearranging the initialization, as brcms_c_regd_init() must
> be called after wiphy->bands has been set up. I don't see any reason why
> setting up the bands couldn't be moved to before channel_mgr_attach()
> though, and in that case regd_init() could be moved into
> channel_mgr_attach().

Please do. I prefer to keep regd_init() local to channel.c.

Gr. AvS


  reply	other threads:[~2012-05-27 12:17 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 [this message]
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
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=4FC21B3F.6090903@broadcom.com \
    --to=arend@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rodrigue@qca.qualcomm.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.