From: Simon Wunderlich <sw@simonwunderlich.de>
To: "Richard Schütz" <rschuetz@uni-koblenz.de>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] wireless: return correct mandatory rates
Date: Fri, 08 Sep 2017 11:33:32 +0200 [thread overview]
Message-ID: <5435234.Pp2Z8V5qmG@prime> (raw)
In-Reply-To: <1f7e466e-2a68-b97a-ee2e-21c3e74a9fc5@uni-koblenz.de>
[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]
Hi,
On Friday, September 8, 2017 10:53:37 AM CEST Richard Schütz wrote:
> Am 08.09.2017 um 10:43 schrieb Richard Schütz:
> > Am 08.09.2017 um 08:55 schrieb Johannes Berg:
> >> On Thu, 2017-09-07 at 17:47 +0200, Richard Schütz wrote:
> >>> Use IEEE80211_RATE_MANDATORY_G instead of IEEE80211_RATE_MANDATORY_B
> >>> for comparison 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.
> >>
> >> This I don't understand - what "comparison" are you talking about?
> >
> > Sorry, I meant the condition that checks for the presence of
> > mandatory_flag at the bottom of the function.
> >
> >>> Also force IEEE80211_RATE_MANDATORY_A for 10 MHz and 5 MHz channels
> >>> as they use "half-clocked" respectively "quarter-clocked" operation
> >>> of the OFDM rates (IEEE Std 802.11-2016, 17.1.1).
> >>
> >> I don't think this is correct - the way the flags are used, anything on
> >> 2.4 GHz would never bother to check the MANDATORY_A flag.
> >
> > Do we actually allow 10 MHz and 5 MHz operation in the 2.4 GHz band? As
> > far as I can tell that has only been specified for OFDM PHYs, which use
> > the 5 GHz band and are covered by IEEE80211_RATE_MANDATORY_A, but I am
> > not a hundred per cent sure about that. Cc'ing Simon Wunderlich who
> > originally implemented checking of scan_width here.
>
> Looks like the old address is invalid now. New try.
>
Yeah, officially only OFDM has the half/quarter clock stuff defined, not ERP (2.4
GHz 11g) or DSSS, and also not HT.
However, technically, the Qualcomm/Atheros hardware (ath9k and ath5k) supports
DSSS or HT on quarter and half rates just fine, also on 2.4 GHz.
I believe we currently support the 5/10 MHz on 2.4 GHz, although we shouldn't
when we follow the standard strictly. The question is if we should follow the
standard strictly - this feature is already quite limited, and people tend to
use the ath9k/ath5k chanbw patch from OpenWRT/LEDE.
Cheers,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-08 9:40 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 [this message]
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
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=5435234.Pp2Z8V5qmG@prime \
--to=sw@simonwunderlich.de \
--cc=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 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.