Linux wireless drivers development
 help / color / mirror / Atom feed
From: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Simon Wunderlich <simon.wunderlich@s2003.tu-chemnitz.de>,
	linux-wireless@vger.kernel.org,
	Johannes Berg <johannes@sipsolutions.net>,
	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 11:58:25 +0200	[thread overview]
Message-ID: <20130517095825.GA1555@pandem0nium> (raw)
In-Reply-To: <CAJ-Vmo=39cS38UCDeQrdJ7x-t=cyr8cnsf3G2opxyeY3KzWLUg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

Hey Adrian,

On Thu, May 16, 2013 at 08:34:39AM -0700, Adrian Chadd wrote:
> How about I setup a couple of FreeBSD devices with 5/10MHz operating
> modes and dump the beacon IEs, probe request/response and assoc
> request/response?
> 
> That way you can see what the rate table entries look like.

yeah, that would be cool to compare the IEs and see if this looks similar.

Maybe I can do the same for the Linux IEs too, just for reference.
We basically enable it only if 802.11a or g is supported (802.11b is not
supported), and announce OFDM only rates. 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.

BTW, how is HT handled for narrow channels in FreeBSD? Do you just send
HT IEs as they are in 20 MHz? Also, do you disable secondary channels?
(I would probably do that, using two adjacent 5 MHz channels should be
replaceable by one 10 MHz channel ...)

Thanks,
	Simon

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-05-17  9:58 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 [this message]
     [not found]         ` <CA+yqC4bY_5Vd=B7nnmjEnDS+gJwD7fFZBkUCKEw0vb0aWucD5Q@mail.gmail.com>
2013-05-17 14:39           ` Johannes Berg
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=20130517095825.GA1555@pandem0nium \
    --to=simon.wunderlich@s2003.tu-chemnitz.de \
    --cc=adrian@freebsd.org \
    --cc=johannes@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