All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Sujith <m.sujith@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Jouni Malinen <Jouni.Malinen@Atheros.com>
Subject: Re: [PATCH] mac80211: Add capability to enable/disable beaconing
Date: Tue, 20 Jan 2009 11:54:44 -0800	[thread overview]
Message-ID: <20090120195444.GE19581@tesla> (raw)
In-Reply-To: <18805.62728.34610.424793@localhost.localdomain>

On Tue, Jan 20, 2009 at 08:00:08AM -0800, Sujith wrote:
> Johannes Berg wrote:
> > 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? :)
> 
> Oh, absolutely :)
> 
> > 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?
> 
> Ok, how about this ?
> 
> diff --git a/include/net/mac80211.h b/include/net/mac80211.h
> index 9a5869e..72a3025 100644
> --- a/include/net/mac80211.h
> +++ b/include/net/mac80211.h
> @@ -624,12 +624,18 @@ struct ieee80211_if_init_conf {
>   * enum ieee80211_if_conf_change - interface config change flags
>   *
>   * @IEEE80211_IFCC_BSSID: The BSSID changed.
> - * @IEEE80211_IFCC_BEACON: The beacon for this interface changed
> - *     (currently AP and MESH only), use ieee80211_beacon_get().
> + * @IEEE80211_IFCC_CONFIGURE_BEACON: The beacon for this interface changed
> + *     (currently AP,IBSS and MESH only), use ieee80211_beacon_get().
> + * @IEEE80211_IFCC_STOP_BEACON: Indicates that beaconing should be stopped
> + *     by the driver.
> + * @IEEE80211_IFCC_RESUME_BEACON: Beaconing can be resumed by the driver,
> + *     with the original template obtained from mac80211.
>   */
>  enum ieee80211_if_conf_change {
> -       IEEE80211_IFCC_BSSID    = BIT(0),
> -       IEEE80211_IFCC_BEACON   = BIT(1),
> +       IEEE80211_IFCC_BSSID            = BIT(0),
> +       IEEE80211_IFCC_CONFIGURE_BEACON = BIT(1),
> +       IEEE80211_IFCC_STOP_BEACON      = BIT(2),
> +       IEEE80211_IFCC_RESUME_BEACON    = BIT(3)

This would make grep'ing easier:

IEEE80211_IFCC_BEACON_CONFIGURE = BIT(1),
IEEE80211_IFCC_BEACON_STOP      = BIT(2),
IEEE80211_IFCC_BEACON_RESUME    = BIT(3)

  Luis

  reply	other threads:[~2009-01-20 19:55 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
2009-01-20 16:00   ` Sujith
2009-01-20 19:54     ` Luis R. Rodriguez [this message]
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=20090120195444.GE19581@tesla \
    --to=lrodriguez@atheros.com \
    --cc=Jouni.Malinen@Atheros.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=m.sujith@gmail.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.