From: "Rafał Miłecki" <zajec5@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Michael Buesch <mb@bu3sch.de>,
"bcm43xx-dev@lists.berlios.de" <bcm43xx-dev@lists.berlios.de>
Subject: Re: [RFC] How to store HT (40MHz) support
Date: Thu, 21 Jan 2010 16:50:20 +0100 [thread overview]
Message-ID: <b170af451001210750t123a94e2r833e075933c06752@mail.gmail.com> (raw)
In-Reply-To: <1263982729.14538.5.camel@johannes.local>
W dniu 20 stycznia 2010 11:18 użytkownik Johannes Berg
<johannes@sipsolutions.net> napisał:
> On Wed, 2010-01-20 at 01:06 +0100, Rafał Miłecki wrote:
>> + phy->use_40mhz = conf_is_ht(conf);
>
> This is wrong, conf_is_ht might also be 20mhz, look at the other
> helpers.
I tried to understand what actually is HT and after reading many
articles I have more knowledge but still I'm not 100% sure.
AFAIU:
1) HT means using more than 1 stream in channel (and can be on any:
20MHz or 40MHz)
2) conf_is_ht(...) checks if mac80211 want us to use more than 1
stream in channel
3) conf_is_ht40_minus(...) checks if we should use frequency below
current as additional 20MHz, so for example for channel 7 which is
2,431->2,453 we should use additinal 20MHz in channel 3 which is
2,411->2,433
4) conf_is_ht40_plus(...) checks if we should use frequency over
current as additional 20MHz, so for example for channel 3 which is
2,411->2,433 we should use additinal 20MHz in channel 7 which is
2,431->2,453
Is that correct?
--
Rafał
next prev parent reply other threads:[~2010-01-21 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 0:06 [RFC] How to store HT (40MHz) support Rafał Miłecki
2010-01-20 10:18 ` Johannes Berg
2010-01-21 15:50 ` Rafał Miłecki [this message]
2010-01-21 17:18 ` Luis R. Rodriguez
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=b170af451001210750t123a94e2r833e075933c06752@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.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