From: Johannes Berg <johannes@sipsolutions.net>
To: Sam Leffler <sleffler@google.com>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
Adrian Chadd <adrian@freebsd.org>,
linux-wireless <linux-wireless@vger.kernel.org>,
Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCHv2 00/18] Add support for 5 and 10 MHz channels
Date: Fri, 17 May 2013 16:39:50 +0200 [thread overview]
Message-ID: <1368801590.18033.7.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+yqC4bY_5Vd=B7nnmjEnDS+gJwD7fFZBkUCKEw0vb0aWucD5Q@mail.gmail.com> (sfid-20130517_163323_137467_9055ADBE)
[You need to stop using HTML, it will never make it to our list :-) ]
> The rates are divided by two or
> four (for 10 and 5 MHz), and rounded up. That's pretty much
> the only
> thing which is changed to 20 MHz.
>
>
> I rounded down; can't remember why; probably because that was what the
> PSB (Public Safety Band) spec said to do.
Which is the PSB spec? The current version of 802.11 (-2012) clearly
wants to round up:
8.4.2.3 Supported Rates element
...
Within Beacon, Probe Response, Association Response,
Reassociation Response, Mesh Peering Open, and Mesh Peering
Confirm management frames, each Supported Rate contained in the
BSSBasicRateSet parameter is encoded as an octet with the MSB
(bit 7) set to 1, and bits 6 to 0 are set to the data rate, if
necessary rounded up to the next 500kb/s, in units of 500 kb/s.
For example, a 2.25 Mb/s rate contained in the BSSBasicRateSet
parameter is encoded as X'85'.
johannes
next prev parent reply other threads:[~2013-05-17 14:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 14:18 [PATCHv2 00/18] Add support for 5 and 10 MHz channels Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 01/18] nl80211/cfg80211: add 5 and 10 MHz defines and wiphy flag Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 02/18] nl80211: add half/quarter channel bitrate tables to supported band struct Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 03/18] mac80211: fix various components for the new 5 and 10 MHz widths Simon Wunderlich
[not found] ` <CA+yqC4a6W6i9TUoEc1Boxe6a5eun_TSjLB0F+w3F2L_Hn+v_gA@mail.gmail.com>
2013-05-15 18:12 ` Johannes Berg
2013-05-15 20:22 ` Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 04/18] mac80211: fix timing for 5 MHz and 10 MHz channels Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 05/18] mac80211: round rates to the next multiple of 500kbps Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 06/18] mac80211: choose bitrate table according to bandwidth Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 07/18] mac80211: add radiotap flag and handling for 5/10 MHz Simon Wunderlich
2013-05-15 14:18 ` [PATCHv2 08/18] cfg80211/mac80211: use reduced txpower for 5 and 10 MHz Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 09/18] mac80211: change IBSS channel state to chandef Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 10/18] nl80211: allow 5 and 10 MHz channels for IBSS Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 11/18] ath9k: always use SIFS times from OFDM for 5/10 MHz Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 12/18] ath9k: use chandef instead of channel_type Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 13/18] ath9k: add and use 5/10 MHz bitrate tables Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 14/18] ath9k: report 5/10 MHz channels Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 15/18] ath9k: announce that ath9k supports 5/10 MHz Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 16/18] ath5k: add and use 5/10 MHz bitrate tables Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 17/18] ath5k: report 5/10 MHz channels Simon Wunderlich
2013-05-15 14:19 ` [PATCHv2 18/18] ath5k: enable support for 5 MHz and 10 " Simon Wunderlich
2013-05-15 20:24 ` [PATCHv2 00/18] Add support for 5 " Simon Wunderlich
2013-05-15 20:59 ` Adrian Chadd
2013-05-16 11:40 ` Simon Wunderlich
2013-05-16 15:34 ` Adrian Chadd
2013-05-17 9:58 ` Simon Wunderlich
[not found] ` <CA+yqC4bY_5Vd=B7nnmjEnDS+gJwD7fFZBkUCKEw0vb0aWucD5Q@mail.gmail.com>
2013-05-17 14:39 ` Johannes Berg [this message]
2013-05-17 15:39 ` 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=1368801590.18033.7.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adrian@freebsd.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=simon.wunderlich@s2003.tu-chemnitz.de \
--cc=siwu@hrz.tu-chemnitz.de \
--cc=sleffler@google.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