linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Chun-Yeow Yeoh <yeohchunyeow@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Beacon interval for Mesh/AP in single interface
Date: Tue, 14 Mar 2017 15:04:35 +0100	[thread overview]
Message-ID: <1489500275.10872.9.camel@sipsolutions.net> (raw)
In-Reply-To: <CAEFj985oo-Dv3dXN7rTTph74mkw_jW=7QrCfEXSjP=OGoexuYg@mail.gmail.com> (sfid-20170309_052218_154549_E223479F)

Hi,

> The introduction of the following patches doesn't allow the AP and
> mesh mode to simultaneously run on a single radio interface due to
> beacon interval for both interfaces by default is different.
> [PATCH] cfg80211: disallow beacon_int_min_gcd with IBSS
> [PATCH] cfg80211: support virtual interfaces with different beacon
> intervals
> [PATCH] cfg80211: validate beacon int as part of iface combinations
> 
> Any suggestion that we could solve this.

Interesting. Did hardware actually support this, and if so, what did it
do?

If that worked, then it'd be reasonable to add the appropriate value to
the interface combinations to let it work as before.

If it didn't really work properly, then we can just fix the defaults to
be compatible?

johannes

  reply	other threads:[~2017-03-14 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  4:22 Beacon interval for Mesh/AP in single interface Chun-Yeow Yeoh
2017-03-14 14:04 ` Johannes Berg [this message]
2017-03-15  8:25   ` Chun-Yeow Yeoh
2017-03-16 10:08     ` 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=1489500275.10872.9.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yeohchunyeow@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 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).