From: Johannes Berg <johannes@sipsolutions.net>
To: Ashok Nagarajan <ashok@cozybit.com>
Cc: linux-wireless@vger.kernel.org, javier@cozybit.com
Subject: Re: [PATCH] {nl,cfg,mac}80211: Enable control quality monitoring for mesh
Date: Fri, 24 Feb 2012 08:18:11 +0100 [thread overview]
Message-ID: <1330067891.3426.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1330050621-8955-1-git-send-email-ashok@cozybit.com> (sfid-20120224_033027_978577_9073776C)
On Thu, 2012-02-23 at 18:30 -0800, Ashok Nagarajan wrote:
> Mesh peer links are established only if average rssi of the peer
> candidate satisfies the threshold. This is not in 802.11s specification
> but was requested by David Fulgham, an open80211s user. This is a way to avoid
> marginal peer links with stations that are barely within range.
>
> Signed-off-by: Ashok Nagarajan <ashok@cozybit.com>
> Signed-off-by: Javier Cardona <javier@cozybit.com>
> ---
> drivers/net/wireless/mac80211_hwsim.c | 1 +
> net/mac80211/cfg.c | 1 +
> net/mac80211/mesh_plink.c | 22 +++++++++++++++++++++-
> net/wireless/nl80211.c | 3 ++-
> 4 files changed, 25 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/wireless/mac80211_hwsim.c b/drivers/net/wireless/mac80211_hwsim.c
> index 4b9e730..ca7d5a6 100644
> --- a/drivers/net/wireless/mac80211_hwsim.c
> +++ b/drivers/net/wireless/mac80211_hwsim.c
> @@ -729,6 +729,7 @@ static int mac80211_hwsim_add_interface(struct ieee80211_hw *hw,
> __func__, ieee80211_vif_type_p2p(vif),
> vif->addr);
> hwsim_set_magic(vif);
> + vif->driver_flags |= IEEE80211_VIF_SUPPORTS_CQM_RSSI;
That isn't right, hwsim does nothing to support CQM.
johannes
next prev parent reply other threads:[~2012-02-24 7:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 2:30 [PATCH] {nl,cfg,mac}80211: Enable control quality monitoring for mesh Ashok Nagarajan
2012-02-24 5:21 ` Javier Cardona
2012-02-24 5:24 ` Javier Cardona
2012-02-24 7:18 ` Johannes Berg [this message]
2012-02-24 7:19 ` Johannes Berg
2012-02-24 16:40 ` Javier Cardona
2012-02-24 16:44 ` 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=1330067891.3426.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ashok@cozybit.com \
--cc=javier@cozybit.com \
--cc=linux-wireless@vger.kernel.org \
/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).