From: "Goldenshtein, Victor" <victorg@ti.com>
To: Felix Fietkau <nbd@openwrt.org>
Cc: hostap@lists.shmoo.com, linux-wireless@vger.kernel.org,
kgiori@qca.qualcomm.com, mcgrof@frijolero.org,
zefir.kurtisi@neratec.com, adrian.chadd@gmail.com, j@w1.fi,
johannes@sipsolutions.net, coelho@ti.com, assaf@ti.com,
yoni.divinsky@ti.com, igalc@ti.com, adrian@freebsd.org
Subject: Re: [RFC 4/7] hostapd: add dfs support into interface init flow
Date: Thu, 26 Jan 2012 15:36:28 +0200 [thread overview]
Message-ID: <CAK80WHaE5u22nA3acCKXAdd_WZkwS+iLjJ5PcDqCwyb6UWUQzg@mail.gmail.com> (raw)
In-Reply-To: <4F2150B2.3030004@openwrt.org>
On Thu, Jan 26, 2012 at 3:10 PM, Felix Fietkau <nbd@openwrt.org> wrote:
>> +
>> + eloop_enable();
>> + wpa_printf(MSG_DEBUG, "Continuing with init flow");
>> }
>>
>> if (iface->current_mode) {
> This seems like a bit of a hack to me. Wouldn't it be better to prevent
> eloop_terminate() from being called instead of adding another function
> to override the eloop termination?
Couldn't find a cleaner way to do it, I mean without the usage of the
eloop_run() + eloop_terminate().
We need to check a DFS channel prior starting the tx, i.e. - listen
for radar event during the initialization flow, prior the
hostapd_global_run(), I would gladly hear other ideas for this
implementation.
--
Thanks,
Victor.
next prev parent reply other threads:[~2012-01-26 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 12:41 [RFC 0/7] hostap: add DFS master ability Victor Goldenshtein
2012-01-26 12:41 ` [RFC 1/7] hostapd: implement dfs drv ops functions Victor Goldenshtein
2012-02-09 23:19 ` Luis R. Rodriguez
2012-02-15 16:47 ` Goldenshtein, Victor
2012-01-26 12:41 ` [RFC 2/7] hostapd: add channel switch ability Victor Goldenshtein
2012-01-26 12:41 ` [RFC 3/7] hostapd: add dfs events Victor Goldenshtein
2012-01-26 12:41 ` [RFC 4/7] hostapd: add dfs support into interface init flow Victor Goldenshtein
2012-01-26 13:10 ` Felix Fietkau
2012-01-26 13:36 ` Goldenshtein, Victor [this message]
2012-01-26 12:41 ` [RFC 5/7] nl80211: add support to enable TX on oper-channel Victor Goldenshtein
2012-01-26 12:41 ` [RFC 6/7] nl80211: add channel switch command/event Victor Goldenshtein
2012-01-26 12:41 ` [RFC 7/7] nl80211: add start radar detection command/event Victor Goldenshtein
2012-01-26 19:27 ` [RFC 0/7] hostap: add DFS master ability David Goodenough
2012-01-30 7:32 ` Goldenshtein, Victor
2012-01-30 10:35 ` David Goodenough
2012-01-30 11:02 ` Julian Calaby
2012-01-30 11:08 ` David Goodenough
2012-02-09 20:18 ` Luis R. Rodriguez
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=CAK80WHaE5u22nA3acCKXAdd_WZkwS+iLjJ5PcDqCwyb6UWUQzg@mail.gmail.com \
--to=victorg@ti.com \
--cc=adrian.chadd@gmail.com \
--cc=adrian@freebsd.org \
--cc=assaf@ti.com \
--cc=coelho@ti.com \
--cc=hostap@lists.shmoo.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@openwrt.org \
--cc=yoni.divinsky@ti.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).