From: Felix Fietkau <nbd@openwrt.org>
To: Victor Goldenshtein <victorg@ti.com>
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 14:10:10 +0100 [thread overview]
Message-ID: <4F2150B2.3030004@openwrt.org> (raw)
In-Reply-To: <1327581689-22090-5-git-send-email-victorg@ti.com>
On 2012-01-26 1:41 PM, Victor Goldenshtein wrote:
> Implement Channel Availability Check (CAC) during initialization
> phase. According to DFS requirements the AP should monitor 'radar
> channels' for potential radar interference for a minimum CAC time
> prior enabling the transmissions.
>
> Add dfs support into hw features, allow the usage of the radar
> channels if ieee80211h is enabled in the hostapd.conf and the
> driver supports radar detection.
>
> Parse and handle driver's DFS capabilities, userspace applications
> must be fully synchronized with device capabilities to detect radar
> patterns in the air which may influence userspace behavior.
>
> Signed-off-by: Boris Presman <boris.presman@ti.com>
> Signed-off-by: Victor Goldenshtein <victorg@ti.com>
> ---
> src/ap/hostapd.c | 17 +++++++++++------
> src/ap/hw_features.c | 30 ++++++++++++++++++++----------
> src/ap/hw_features.h | 9 +++++++++
> src/drivers/driver.h | 5 +++++
> src/drivers/driver_nl80211.c | 7 +++++++
> src/utils/eloop.c | 4 ++++
> src/utils/eloop.h | 7 +++++++
> 7 files changed, 63 insertions(+), 16 deletions(-)
>
> diff --git a/src/ap/hostapd.c b/src/ap/hostapd.c
> index ce37922..411b681 100644
> --- a/src/ap/hostapd.c
> +++ b/src/ap/hostapd.c
> @@ -733,14 +739,13 @@ int hostapd_setup_interface_complete(struct hostapd_iface *iface, int err)
> hostapd_hw_mode_txt(hapd->iconf->hw_mode),
> hapd->iconf->channel, iface->freq);
>
> - if (hostapd_set_freq(hapd, hapd->iconf->hw_mode, iface->freq,
> - hapd->iconf->channel,
> - hapd->iconf->ieee80211n,
> - hapd->iconf->secondary_channel)) {
> - wpa_printf(MSG_ERROR, "Could not set channel for "
> - "kernel driver");
> + if (hostapd_check_set_freq(hapd)) {
> + wpa_printf(MSG_ERROR, "Couldn't check/set freq");
> return -1;
> }
> +
> + 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?
- Felix
next prev parent reply other threads:[~2012-01-26 13:10 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 [this message]
2012-01-26 13:36 ` Goldenshtein, Victor
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=4F2150B2.3030004@openwrt.org \
--to=nbd@openwrt.org \
--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=victorg@ti.com \
--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 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.