From: Johannes Berg <johannes@sipsolutions.net>
To: sbrown@cortland.com
Cc: Ben Greear <greearb@candelatech.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: restrict AP beacon intervals
Date: Mon, 09 May 2011 19:28:51 +0200 [thread overview]
Message-ID: <1304962131.12202.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1304961656.2615.9.camel@mythtv.ewol.com> (sfid-20110509_192125_083264_329C5406)
On Mon, 2011-05-09 at 13:20 -0400, Steve Brown wrote:
> >
> > If you really care greatly about having different beacon intervals (and
> > I don't see why you would?) then maybe you can think how we can enforce
> > and advertise that to userspace. For now, I'm more comfortable just
> > restricting it.
> >
> > johannes
>
> I posted a patch for different beacon intervals to the ath9k list last
> Jan. This was to allow both a mesh (interval 1000) and ap (interval 100)
> vif on the same radio. This combination seems useful, at least for me.
Yeah that makes some sense. Note that this patch doesn't (yet) enforce
any restrictions on mesh anyway though.
johannes
next prev parent reply other threads:[~2011-05-09 17:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 16:41 [PATCH] cfg80211: restrict AP beacon intervals Johannes Berg
2011-05-09 16:46 ` Ben Greear
2011-05-09 16:49 ` Johannes Berg
2011-05-09 16:53 ` Ben Greear
2011-05-09 16:55 ` Johannes Berg
2011-05-09 17:20 ` Steve Brown
2011-05-09 17:28 ` Johannes Berg [this message]
2011-05-10 20:46 ` Ben Greear
2011-05-11 15:58 ` Björn Smedman
2011-05-11 16:48 ` Johannes Berg
2011-05-11 17:10 ` Ben Greear
2011-05-11 17:17 ` Johannes Berg
2011-05-11 21:39 ` Björn Smedman
2011-05-12 8:14 ` Johannes Berg
2011-05-12 18:08 ` Björn Smedman
2011-05-12 18:13 ` 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=1304962131.12202.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sbrown@cortland.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).