From: Johannes Berg <johannes@sipsolutions.net>
To: Sujith <Sujith.Manoharan@atheros.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Jouni.Malinen@Atheros.com
Subject: Re: [PATCH] mac80211: Add capability to enable/disable beaconing
Date: Tue, 20 Jan 2009 11:52:59 +0100 [thread overview]
Message-ID: <1232448779.20158.4.camel@johannes.local> (raw)
In-Reply-To: <18805.33791.193195.755178@gargle.gargle.HOWL>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
cOn Tue, 2009-01-20 at 13:27 +0530, Sujith wrote:
> This patch adds a flag to notify drivers to start and
> stop beaconing when needed, for example, during a scan run.
> + if ((changed & IEEE80211_IFCC_BEACON) &&
> + (sdata->vif.type == NL80211_IFTYPE_AP ||
> + sdata->vif.type == NL80211_IFTYPE_ADHOC ||
> + sdata->vif.type == NL80211_IFTYPE_MESH_POINT)) {
> + if (local->sw_scanning || local->hw_scanning)
> + conf.enable_beacon = false;
> + else
> + conf.enable_beacon = true;
> + }
> +
You really just want to do the minimal thing, right? :)
That won't work when userspace disables the beacon by removing it, for
instance, right now drivers won't know when hostapd removed the beacon
except that ieee80211_beacon_get will start returning 0... Also, I think
a separate change flag would be appropriate, sometimes we might just
re-enable the beacon without having changed it, after scanning?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-01-20 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 7:57 [PATCH] mac80211: Add capability to enable/disable beaconing Sujith
2009-01-20 10:52 ` Johannes Berg [this message]
2009-01-20 16:00 ` Sujith
2009-01-20 19:54 ` Luis R. Rodriguez
2009-01-21 11:45 ` Johannes Berg
2009-01-21 13:02 ` Johannes Berg
2009-01-22 3:28 ` Sujith
-- strict thread matches above, loose matches on Subject: below --
2009-01-22 17:07 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=1232448779.20158.4.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Jouni.Malinen@Atheros.com \
--cc=Sujith.Manoharan@atheros.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).