From: Johannes Berg <johannes@sipsolutions.net>
To: a@pandem0nium.sipsolutions.net
Cc: linux-wireless@vger.kernel.org,
Mathias Kretschmer <mathias.kretschmer@fokus.fraunhofer.de>,
Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Subject: Re: [PATCH 0/8] Add support for 5 and 10 MHz channels
Date: Fri, 10 May 2013 09:26:16 +0200 [thread overview]
Message-ID: <1368170776.8390.4.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1368123036-22721-1-git-send-email-a>
On Thu, 2013-05-09 at 20:10 +0200, a@pandem0nium wrote:
> Comments:
> * Is there any special requirement for handling beacons? For example,
> rates are halfed or quartered, but some rates could not be represented
> in the rate IEs. For example, 2.25 mbit/s can not be represented as
> multiple of 500 kbps.
> * therefore, all rates are handled like the corresponding 20 MHz
> rates
> internally, which makes a lot of things easier (no changes required
> for rc-algos, beacon creation, etc...). We might consider adjusting
> the
> output of rates for nl80211 or radiotap, though.
This seems completely wrong, since Clause 18 says:
The OFDM system also provides a “half-clocked” operation using
10 MHz channel spacings with data communications capabilities of
3, 4.5, 6, 9, 12, 18, 24, and 27 Mb/s. The support of
transmitting and receiving at data rates of 3, 6, and 12 Mb/s is
mandatory when using 10 MHz channel spacing. The half-clocked
operation doubles symbol times and clear channel assessment
(CCA) times when using 10 MHz channel spacing. The regulatory
requirements and information regarding use of this OFDM PHY are
in Annex D and Annex E.
IOW, it treats the rates as actually the rate they should be. Besides,
what's so hard about rounding up? (8.4.2.4)
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.
I also think you really need to handle this. If you just want a hack for
5/10 MHz, you can put it into drivers' debugfs, if not, then it should
be done properly :-)
johannes
next prev parent reply other threads:[~2013-05-10 7:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 18:10 [PATCH 0/8] Add support for 5 and 10 MHz channels a
2013-05-09 18:10 ` [PATCH 1/8] nl80211/cfg80211: add 5 and 10 MHz defines and wiphy flag a
2013-05-09 18:10 ` [PATCH 2/8] mac80211: fix various components for the new 5 and 10 MHz widths a
2013-05-09 18:31 ` Felix Fietkau
2013-05-09 19:46 ` Simon Wunderlich
2013-05-09 20:32 ` Felix Fietkau
2013-05-09 18:10 ` [PATCH 3/8] mac80211: change IBSS channel state to chandef a
2013-05-09 18:10 ` [PATCH 4/8] mac80211: fix timing for 5 MHz and 10 MHz channels a
2013-05-09 18:10 ` [PATCH 5/8] nl80211: allow 5 and 10 MHz channels for IBSS a
2013-05-09 18:10 ` [PATCH 6/8] ath9k: convert to chandef, enable support for 5/10 MHz channels a
2013-05-09 18:10 ` [PATCH 7/8] ath9k: announce that ath9k supports 5/10 MHz a
2013-05-09 18:10 ` [PATCH 8/8] ath5k: enable support for 5 MHz and 10 MHz channels a
2013-05-09 18:20 ` [PATCH 0/8] Add support for 5 " Simon Wunderlich
2013-05-10 7:26 ` Johannes Berg [this message]
2013-05-10 9:12 ` Adrian Chadd
2013-05-10 9:32 ` Simon Wunderlich
2013-05-10 9:34 ` Johannes Berg
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=1368170776.8390.4.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=a@pandem0nium.sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mathias.kretschmer@fokus.fraunhofer.de \
--cc=siwu@hrz.tu-chemnitz.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).