From: Victor Goldenshtein <victorg@ti.com>
To: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
<linux-wireless@vger.kernel.org>, <kgiori@qca.qualcomm.com>,
<mcgrof@frijolero.org>, <zefir.kurtisi@neratec.com>,
<adrian.chadd@gmail.com>, <j@w1.fi>, <coelho@ti.com>,
<igalc@ti.com>, <adrian@freebsd.org>, <nbd@nbd.name>,
<victorgld@gmail.com>
Subject: Re: [PATCH v4 1/6] nl80211/cfg80211: add radar detection command/event
Date: Tue, 20 Nov 2012 17:14:59 +0200 [thread overview]
Message-ID: <50AB9E73.3090802@ti.com> (raw)
In-Reply-To: <20121113180505.GB19223@pandem0nium>
On 13/11/2012 20:05, Simon Wunderlich wrote:
> On Tue, Nov 13, 2012 at 05:04:03PM +0200, Victor Goldenshtein wrote:
>> On 05/11/2012 17:21, Johannes Berg wrote:
>>> On Thu, 2012-11-01 at 09:54 +0200, Victor Goldenshtein wrote:
>>>> On 22/10/2012 14:55, Johannes Berg wrote:
>>>>>> 2. In __nl80211_set_channel() - to cover the case when the CAC was
>>>>>> initiated on a "preset_chan" (during AP init phase) and the IF was
>>>>>> removed before the AP was even started (local->oper_channel wasn't set yet).
>>>>>
>>>>> Hmm, I'm not sure I get it. How is "local->oper_channel" (a mac80211
>>>>> variable) related to this cfg80211 code?
>>>>
>>>> It's not, just saying that its not set at this point.
>>>>
>>>>> start_ap() isn't expected to be able to succeed until CAC passed
>>>>> successfully, but OTOH the channel isn't configured until then?
>>>>
>>>> right, the initial CAC performed before start_ap(), only by setting the
>>>> channel with __nl80211_set_channel() + radar detection command.
>>>
>>> Hmm. Maybe then the channel should be passed to the radar detection
>>> command instead? That way, it can be passed through, you can allocate a
>>> channel context, etc. Much easier?
>>
>> We already pass the frequency in the radar detection command, the
>> set channel operation comes during hostapd init flow regardless DFS
>> implementation.
>
> Just for clarification for the API: Is the driver required to (re)set the channel
> itself in the radar detection command, or do we expect that the channel was already
> set via __nl80211_set_channel() (or other means) before?
>
> This would be important for other DFS modes like IBSS later.
>
Already discussed this privately, still maybe someone else also interested.
The set channel operation is relevant only during initial CAC test,
it set and re-set (if necessary - e.g. radar detected on the first
channel) by the hostapd it self, so the driver doesn't required to set
the channel in the radar detection command.
--
Thanks,
Victor.
next prev parent reply other threads:[~2012-11-20 15:16 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 14:48 [PATCH v4 0/6] nl/cfg/mac80211: add DFS master ability Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 1/6] nl80211/cfg80211: add radar detection command/event Victor Goldenshtein
2012-10-16 19:01 ` Johannes Berg
2012-10-17 16:20 ` Zefir Kurtisi
2012-10-17 16:23 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:55 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:21 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-11-13 18:05 ` Simon Wunderlich
2012-11-20 15:14 ` Victor Goldenshtein [this message]
2012-11-26 10:52 ` Johannes Berg
2012-11-14 11:19 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-14 12:32 ` Michal Kazior
2012-11-14 12:38 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:51 ` Johannes Berg
2012-10-14 14:48 ` [PATCH v4 2/6] mac80211: " Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 3/6] nl80211/cfg80211: add ability to enable TX on op-channel Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 4/6] mac80211: " Victor Goldenshtein
2012-10-16 19:03 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 5/6] nl80211/cfg80211: add ap channel switch command Victor Goldenshtein
2012-10-16 19:06 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:52 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:27 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-10-23 6:20 ` Michal Kazior
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-01 17:15 ` Adrian Chadd
2012-11-01 19:32 ` Johannes Berg
2012-11-05 15:29 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-10-14 14:48 ` [PATCH v4 6/6] mac80211: add ap channel switch command/event Victor Goldenshtein
2012-10-16 19:07 ` Johannes Berg
2012-10-21 16:40 ` Victor Goldenshtein
2012-10-22 12:56 ` Johannes Berg
2012-11-01 7:54 ` Victor Goldenshtein
2012-11-05 15:23 ` Johannes Berg
2012-11-13 15:04 ` Victor Goldenshtein
2012-11-14 11:23 ` Johannes Berg
2012-11-14 12:19 ` Michal Kazior
2012-11-14 12:38 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:50 ` Johannes Berg
2012-11-20 15:15 ` Victor Goldenshtein
2012-11-26 10:50 ` 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=50AB9E73.3090802@ti.com \
--to=victorg@ti.com \
--cc=adrian.chadd@gmail.com \
--cc=adrian@freebsd.org \
--cc=coelho@ti.com \
--cc=igalc@ti.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kgiori@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.org \
--cc=nbd@nbd.name \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=victorgld@gmail.com \
--cc=zefir.kurtisi@neratec.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 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).