From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: Avinash Patil <patila@marvell.com>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>,
Amitkumar Karwar <akarwar@marvell.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Cathy Luo <cluo@marvell.com>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] cfg80211: do not check for carrier during start_radar_detect
Date: Wed, 07 Jan 2015 13:55:00 +0100 [thread overview]
Message-ID: <1420635300.3407.5.camel@sipsolutions.net> (raw)
In-Reply-To: <CALhHN=qA7icuY_MNvBebDsOMOkh6hEsWNkrZoGDGsQg+-f6Xog@mail.gmail.com> (sfid-20141201_081337_327722_EAB90EE5)
On Mon, 2014-12-01 at 08:13 +0100, Janusz Dziedzic wrote:
> Seems this patch unlock off-channel CAC (we are connected/ap started
> and detect radar on other channel), but seem mac80211 don't support
> this correctly now.
Come to think of it - I don't believe there's any way to do off-channel
CAC properly since you'd be out of your operating channel for like a
minute - might as well tear down the AP then.
johannes
next prev parent reply other threads:[~2015-01-07 12:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 16:35 [PATCH] cfg80211: do not check for carrier during start_radar_detect Avinash Patil
2014-12-01 7:13 ` Janusz Dziedzic
[not found] ` <5FF020A1CFFEEC49BD1E09530C4FF5951B160B81A7@SC-VEXCH1.marvell.com>
2014-12-23 10:13 ` Avinash Patil
2014-12-23 10:26 ` Johannes Berg
2014-12-23 10:30 ` Avinash Patil
2014-12-23 10:36 ` Johannes Berg
2014-12-23 10:37 ` Johannes Berg
2014-12-23 11:32 ` Avinash Patil
2014-12-23 12:01 ` Johannes Berg
2015-01-07 12:55 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-28 11:28 Avinash Patil
2014-11-28 15:11 ` Johannes Berg
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=1420635300.3407.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akarwar@marvell.com \
--cc=cluo@marvell.com \
--cc=janusz.dziedzic@tieto.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=patila@marvell.com \
--cc=siwu@hrz.tu-chemnitz.de \
/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).