From: Johannes Berg <johannes@sipsolutions.net>
To: "Richard Schütz" <rschuetz@uni-koblenz.de>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2 2/2] wireless: return correct mandatory rates
Date: Thu, 21 Sep 2017 15:52:06 +0200 [thread overview]
Message-ID: <1506001926.2048.5.camel@sipsolutions.net> (raw)
In-Reply-To: <20170908160712.8765-1-rschuetz@uni-koblenz.de> (sfid-20170908_180746_422254_8173A2C4)
On Fri, 2017-09-08 at 18:07 +0200, Richard Schütz wrote:
> Use IEEE80211_RATE_MANDATORY_G instead of IEEE80211_RATE_MANDATORY_B
> to get
> all mandatory rates in 2.4 GHz band. It is safe to do so because ERP
> mandatory rates are a superset of HR/DSSS mandatory rates. Also limit
> to
> OFDM rates for 10 MHz and 5 MHz channels as originally intended by
> commit
> 74608aca4d82e.
I don't understand this. Why should all ERP (Clause 18, 11g) rates be
mandatory for the users of this?
The way I see it, this would make us assume that all 2.4 GHz clients
support ERP in IBSS, which may not be true?
johannes
next prev parent reply other threads:[~2017-09-21 13:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 15:47 [PATCH 1/2] wireless: set correct mandatory rate flags Richard Schütz
2017-09-07 15:47 ` [PATCH 2/2] wireless: return correct mandatory rates Richard Schütz
2017-09-08 6:55 ` Johannes Berg
2017-09-08 8:43 ` Richard Schütz
2017-09-08 8:53 ` Richard Schütz
2017-09-08 9:33 ` Simon Wunderlich
2017-09-08 9:03 ` Johannes Berg
2017-09-08 10:10 ` Richard Schütz
2017-09-08 10:12 ` Johannes Berg
2017-09-08 16:07 ` [PATCH v2 " Richard Schütz
2017-09-21 13:52 ` Johannes Berg [this message]
2017-09-22 10:09 ` Richard Schütz
2017-09-22 10:28 ` Johannes Berg
2017-09-08 6:54 ` [PATCH 1/2] wireless: set correct mandatory rate flags Johannes Berg
2017-09-08 8:43 ` Richard Schütz
2017-09-08 8:57 ` Johannes Berg
2017-09-21 13:49 ` Johannes Berg
2018-01-26 22:17 ` Matthias Schiffer
2018-01-30 7:43 ` Johannes Berg
2018-01-30 10:47 ` Matthias Schiffer
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=1506001926.2048.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rschuetz@uni-koblenz.de \
/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).