MIME-Version: 1.0
In-Reply-To: <CAB3XZEfJt=YKP8+SKie7L_4sdxcdrGUtzruDvrjFKDvXKo2L3w@mail.gmail.com>
References: <1420645811-17877-1-git-send-email-eliad@wizery.com>
	<1420645811-17877-3-git-send-email-eliad@wizery.com>
	<20150207115758.GA503@w1.fi>
	<CALhHN=rj=1OE8xv_q4cTRVkF_=Ko-3amjn4_6tYHXg9dtev=9A@mail.gmail.com>
	<CAB3XZEfJt=YKP8+SKie7L_4sdxcdrGUtzruDvrjFKDvXKo2L3w@mail.gmail.com>
Date: Sun, 8 Feb 2015 14:17:49 +0100
Message-ID: <CALhHN=pxxL9Wr9aURjZV8fQ7uvSV6e49KTLbEAzUZ0zTDhPsqw@mail.gmail.com> (sfid-20150208_141754_003991_76752CE4)
Subject: Re: [PATCH v2 3/3] mac80211: don't defer scans in case of radar detection
From: Janusz Dziedzic <janusz.dziedzic@tieto.com>
To: Eliad Peller <eliad@wizery.com>
Cc: Jouni Malinen <j@w1.fi>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-wireless-owner@vger.kernel.org

On 8 February 2015 at 11:57, Eliad Peller <eliad@wizery.com> wrote:
> On Sat, Feb 7, 2015 at 9:17 PM, Janusz Dziedzic
> <janusz.dziedzic@tieto.com> wrote:
>> BTW, what in case we will start AP on first interface (DFS channel),
>> on second one we will try to connect to other AP. As I understand this
>> correctly, second iface (STA iface) will not allow to scan (connect)
>> ...?
>>
> right.
> The rationale behind it that you must listen constantly to detect
> radar events, which prevents scanning off-channel.
> (i guess an exception for on-channel scanning can be added if needed, though)
>
Still I can image hw with hw_scan() support that could have dedicated
"hw part" for scanning.
So, driver should made this decision (allow or not) base on hw features.

BR
Janusz

>> Other case, what if we start DFS AP and allow to scan in AP mode (eg
>> for ACS purpose, allow to choose better channel and do CSA ...)?
> ditto. you just have to make sure you keep listening on the operating channel.
>
> Eliad.