From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "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 09:46:25 -0700 [thread overview]
Message-ID: <4DC81A61.9080101@candelatech.com> (raw)
In-Reply-To: <1304959275.12202.4.camel@jlt3.sipsolutions.net>
On 05/09/2011 09:41 AM, Johannes Berg wrote:
> From: Johannes Berg<johannes.berg@intel.com>
>
> Multiple virtual AP interfaces can currently try
> to use different beacon intervals, but that just
> leads to problems since it won't actually be done
> that way by drivers. Return an error in this case
> to make sure it won't be done wrong.
I think there is no problem with having different beacon
intervals, as long as they are all a multiple of
the smallest interval and the driver does things properly.
I'm not sure ath9k or ath5k currently supports this properly,
but there was a patch floating around for a while that did
this for ath9k I think...
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-09 16:46 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 [this message]
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
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=4DC81A61.9080101@candelatech.com \
--to=greearb@candelatech.com \
--cc=johannes@sipsolutions.net \
--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).