Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Nils Bagge <nbagge@bandspeed.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: RE: HT capabilities IE
Date: Fri, 10 Oct 2008 11:17:48 +0200	[thread overview]
Message-ID: <1223630268.3930.75.camel@johannes.berg> (raw)
In-Reply-To: <6EACAD9615B47B42A780C005414307E1014956CE@mars.bandspeed.com>

[-- Attachment #1: Type: text/plain, Size: 739 bytes --]

On Thu, 2008-10-09 at 10:41 -0500, Nils Bagge wrote:
> > Right, but if you enter dynamic SM PS then it doesn't matter much
> > anyway, does it? I mean, there's no protection requirement in that
> > case, is there? Or am I reading it wrong? I _think_ I will handle the
> > SM PS change in mac80211, but I'm not entirely sure right now.
> > 
> > Johannes
> 
> 
> Well, upon a more careful reading of 11.2.3, the second paragraph would
> seem to indicate that some kind of protection/wake-up is required prior
> to a multi-spatial stream transmission, if the receiver is in dynamic SM
> power save mode.

Indeed, I was reading that as "beginning of the frame" rather than
"beginning of the frame sequence". Sorry.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2008-10-10  9:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08 10:01 HT capabilities IE Johannes Berg
2008-10-08 12:40 ` Tomas Winkler
2008-10-08 13:30   ` Tomas Winkler
2008-10-09  9:49     ` Johannes Berg
2008-10-08 15:33 ` Nils Bagge
2008-10-09  9:54   ` Johannes Berg
2008-10-09 15:41     ` Nils Bagge
2008-10-10  9:17       ` Johannes Berg [this message]
2008-10-09 16:33     ` Tomas Winkler

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=1223630268.3930.75.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbagge@bandspeed.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