From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>,
Purushottam Kushwaha <pkushwah@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, jouni@qca.qualcomm.com,
usdutt@qti.qualcomm.com, ganeshk@qti.qualcomm.com,
mkalikot@qca.qualcomm.com, amarnath@qca.qualcomm.com
Subject: Re: [PATCH v2] cfg80211: Allow differnt beacon interval if driver supports
Date: Mon, 18 Jul 2016 21:14:04 +0200 [thread overview]
Message-ID: <1468869244.2944.3.camel@sipsolutions.net> (raw)
In-Reply-To: <578D2846.5060600@candelatech.com>
On Mon, 2016-07-18 at 12:04 -0700, Ben Greear wrote:
>
> On 07/18/2016 11:56 AM, Johannes Berg wrote:
> > On Mon, 2016-07-18 at 19:23 +0530, Purushottam Kushwaha wrote:
> > > Driver may allow support for different beacon interval on virtual
> > > interfaces.
> > > Allow if such support is advertised by driver. This adds new
> > > ext_feature as NL80211_EXT_FEATURE_DIFF_BEACON_INTERVAL.
> >
> > We have NL80211_IFACE_COMB_STA_AP_BI_MATCH in interface
> > combinations,
> > perhaps it would make sense to also put this flag there?
>
> I was under impression that ath9k had supported this for years,
> but I guess I haven't tested it lately....
>
It may very well have, but if userspace can't rely on it because other
drivers don't then it's pretty pointless.
johannes
next prev parent reply other threads:[~2016-07-18 19:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 13:53 [PATCH v2] cfg80211: Allow differnt beacon interval if driver supports Purushottam Kushwaha
2016-07-18 16:25 ` Kalle Valo
2016-07-18 18:56 ` Johannes Berg
2016-07-18 19:04 ` Ben Greear
2016-07-18 19:14 ` Johannes Berg [this message]
2016-07-18 19:31 ` Ben Greear
2016-07-18 19:13 ` Arend Van Spriel
2016-07-18 19:15 ` Johannes Berg
2016-07-18 19:21 ` Arend Van Spriel
2016-07-18 19:22 ` Johannes Berg
2016-07-20 13:15 ` Undekari, Sunil Dutt
2016-07-18 19:35 ` Arend Van Spriel
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=1468869244.2944.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=amarnath@qca.qualcomm.com \
--cc=ganeshk@qti.qualcomm.com \
--cc=greearb@candelatech.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mkalikot@qca.qualcomm.com \
--cc=pkushwah@qti.qualcomm.com \
--cc=usdutt@qti.qualcomm.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