From: "Arend van Spriel" <arend@broadcom.com>
To: "Adrian Chadd" <adrian@freebsd.org>
Cc: "Ben Greear" <greearb@candelatech.com>,
"Kelly Hogan" <kshogan@bluemesh.net>,
linux-wireless@vger.kernel.org
Subject: Re: Is Multi-Vif (vaps) Different Channel Operation Supported?
Date: Sat, 27 Oct 2012 20:19:11 +0200 [thread overview]
Message-ID: <508C259F.8010909@broadcom.com> (raw)
In-Reply-To: <CAJ-Vmo=eP8EC2760A_0Ydy3bvG93bhVXfHS9TS3VpAf2vejJ=g@mail.gmail.com>
On 10/27/2012 10:19 AM, Adrian Chadd wrote:
> Yeah, how's hostap mode supposed to work in that case? The hostap
> interface doesn't go into and out of power save like stations can. It
> has to be ready to receive anything from any STA, at any point in
> time.
In my Intersil/Conexant days there was a marketing dude coming up with
'time-slicing AP' and there was a way to signal STAs the AP was not able
to receive. Just needed to be back in time to send its beacon. I chose
to forget all about the bad idea.
Gr. AvS
next prev parent reply other threads:[~2012-10-27 18:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 10:13 [PATCH 0/4] multi-channel/interface TX power handling Johannes Berg
2012-10-24 10:13 ` [PATCH 1/4] nl80211: move "can set channel" check Johannes Berg
2012-10-24 10:13 ` [PATCH 2/4] cfg80211: make TX power setting per interface Johannes Berg
2012-10-24 16:27 ` Ben Greear
2012-10-24 17:31 ` Johannes Berg
2012-10-24 17:38 ` Ben Greear
2012-10-24 10:13 ` [PATCH 3/4] mac80211: handle TX power per virtual interface Johannes Berg
2012-10-24 10:13 ` [PATCH 4/4] mac80211_hwsim: print per interface TX power Johannes Berg
2012-10-24 15:40 ` [PATCH 0/4] multi-channel/interface TX power handling Ben Greear
2012-10-24 15:42 ` Johannes Berg
2012-10-24 16:31 ` Ben Greear
2012-10-24 17:30 ` Johannes Berg
2012-10-24 17:39 ` Ben Greear
2012-10-24 23:05 ` Is Multi-Vif (vaps) Different Channel Operation Supported? Kelly Hogan
2012-10-24 23:56 ` Ben Greear
2012-10-27 8:19 ` Adrian Chadd
2012-10-27 18:19 ` Arend van Spriel [this message]
2012-10-28 22:06 ` Adrian Chadd
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=508C259F.8010909@broadcom.com \
--to=arend@broadcom.com \
--cc=adrian@freebsd.org \
--cc=greearb@candelatech.com \
--cc=kshogan@bluemesh.net \
--cc=linux-wireless@vger.kernel.org \
/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.