Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Karl Beldan <karl.beldan@rivierawaves.com>
Subject: Re: [PATCH] mac80211: always pick a basic rate to tx RTS/CTS for pre-HT rates
Date: Tue, 09 Apr 2013 13:16:55 +0200	[thread overview]
Message-ID: <1365506215.8465.41.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130409111028.GB27875@magnum.frso.rivierawaves.com> (sfid-20130409_131418_369760_89FEFF28)

On Tue, 2013-04-09 at 13:10 +0200, Karl Beldan wrote:

> > Oh, oops, confused. But then you look at 9.7.6.2 "Rate selection for
> > control frames that initiate a TXOP", which just mandates that you use
> > any rate that the receiver supports, so why bother doing basic rates
> > etc. at all?
> > 
> 
> This chapter precisely, however it reads:
> {
> "If a control frame other than a Basic BlockAckReq or Basic BlockAck is
> carried in a non-HT PPDU, the transmitting STA shall transmit the frame
> using one of the rates in the BSSBasicRateSet parameter or a rate from
> the mandatory rate set of the attached PHY if the BSSBasicRateSet is
> empty."
> }

Oh, right. I'll review the patch again I guess :-)

johannes


  reply	other threads:[~2013-04-09 11:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-05 10:06 [PATCH] mac80211: always pick a basic rate to tx RTS/CTS for pre-HT rates Karl Beldan
2013-04-09 10:29 ` Johannes Berg
2013-04-09 10:55   ` Karl Beldan
2013-04-09 11:05     ` Johannes Berg
2013-04-09 11:10       ` Karl Beldan
2013-04-09 11:16         ` Johannes Berg [this message]
2013-04-09 11:21           ` Karl Beldan
2013-04-11 10:02 ` Johannes Berg
2013-04-11 10:42   ` Karl Beldan

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=1365506215.8465.41.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=karl.beldan@gmail.com \
    --cc=karl.beldan@rivierawaves.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox