From: Seth Forshee <seth.forshee@canonical.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Brett Rudley <brudley@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
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 05/10] brcm80211: smac: remove DFS channels from 5GHz band
Date: Mon, 4 Jun 2012 08:19:09 -0500 [thread overview]
Message-ID: <20120604131909.GA18673@thinkpad-t410> (raw)
In-Reply-To: <4FCBCCFC.7000905@broadcom.com>
On Sun, Jun 03, 2012 at 10:45:48PM +0200, Arend van Spriel wrote:
> On 06/01/2012 08:16 PM, Seth Forshee wrote:
> > On Fri, Jun 01, 2012 at 05:52:55PM +0000, Brett Rudley wrote:
> >>
> >> Not quite understanding this. Why does a STA need radar detection when the NO_IBSS flag is set?
> >
> > Arend specifically suggested removing these channels due to lack of DFS
> > support [1]. I replied asking whether it was at least possible to detect
> > radar presence and stop transmitting in order to be able to use these
> > channels. The last response from Arend was that he was going to check on
> > the firmware capabilities.
>
> I did not follow up with you, but I exchanged some emails with Brett on
> this. As brcmsmac does not support AP mode (yet) it does not need radar
> detection. Detection and appropriate action is coordinated by the AP.
>
> > I'm more than happy to drop this patch if there's not regulatory
> > impedement to operating on the DFS channels.
> >
>
> Let's drop it then. Sorry for not informing you sooner. I will have a
> look at the other patches as well.
No problem. I dropped the patch locally on Friday and have been running
with it over the weekend. I'll wailt a bit longer before resending to
see if you notice anything else that should be changed.
Seth
next prev parent reply other threads:[~2012-06-04 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 16:15 [PATCH 00/10] brcm80211: smac: rework regulatory support Seth Forshee
2012-06-01 16:15 ` [PATCH 01/10] brcm80211: smac: don't set up tx power limits during initialization Seth Forshee
2012-06-01 16:15 ` [PATCH 02/10] brcm80211: smac: always set channel specified by mac80211 Seth Forshee
2012-06-01 16:15 ` [PATCH 03/10] brcm80211: smac: remove unused code for 40MHz channels Seth Forshee
2012-06-01 16:15 ` [PATCH 04/10] brcm80211: smac: clean up channel.c Seth Forshee
2012-06-01 16:15 ` [PATCH 05/10] brcm80211: smac: remove DFS channels from 5GHz band Seth Forshee
2012-06-01 17:52 ` Brett Rudley
2012-06-01 18:16 ` Seth Forshee
2012-06-01 18:38 ` Brett Rudley
2012-06-03 20:45 ` Arend van Spriel
2012-06-04 13:19 ` Seth Forshee [this message]
2012-06-01 16:15 ` [PATCH 06/10] brcm80211: smac: inform mac80211 of the X2 regulatory domain Seth Forshee
2012-06-01 16:15 ` [PATCH 07/10] brcm80211: smac: enable/disable radio on regulatory updates Seth Forshee
2012-06-01 16:15 ` [PATCH 08/10] brcm80211: smac: use mac80211 channel data for tx power limits Seth Forshee
2012-06-01 16:15 ` [PATCH 09/10] brcm80211: smac: don't validate channels against internal regulatory data Seth Forshee
2012-06-01 16:15 ` [PATCH 10/10] brcm80211: smac: use current regulatory domain when checking whether OFDM is allowed 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=20120604131909.GA18673@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 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.