From: Ben Greear <greearb@candelatech.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: Felix Fietkau <nbd@openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Scanning and channel types.
Date: Sun, 06 Feb 2011 13:07:15 -0800 [thread overview]
Message-ID: <4D4F0D83.4040401@candelatech.com> (raw)
In-Reply-To: <AANLkTin6ia8mYsS4LOFTyZoD-dKUgUBGo6uMFt=FjTcY@mail.gmail.com>
On 02/06/2011 12:23 PM, Daniel Halperin wrote:
> Could be rate selection.
>
> Ben, a sanity check: is it possible for the device to be associated
> to an "HT-Only" AP and thus not be able to sent NO_HT packets? Could
> that be why there might need to be a channel change sometimes?
I don't know. The code and comments in ieee80211_set_channel_type
make me think that it's always possible to send NO_HT packets regardless
of hardware's channel type.
One thing I haven't figured out yet: What actually tells the
hardware to send NO_HT v/s HT20 v/s HT40, etc. I have previously tested
HT20 STAs concurrent with HT40 stas, and both can send/receive at once
while the hardware stays in HT40 mode.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-02-06 21:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 19:01 Scanning and channel types Ben Greear
2011-02-06 19:42 ` Felix Fietkau
2011-02-06 19:54 ` Ben Greear
2011-02-06 19:59 ` Felix Fietkau
2011-02-06 20:07 ` Ben Greear
2011-02-06 20:23 ` Daniel Halperin
2011-02-06 21:07 ` Ben Greear [this message]
2011-02-06 21:09 ` Felix Fietkau
2011-02-07 5:42 ` Daniel Halperin
2011-02-07 18:03 ` Ben Greear
2011-02-07 18:32 ` Daniel Halperin
2011-02-07 20:04 ` Ben Greear
2011-02-07 20:10 ` Daniel Halperin
2011-02-07 21:01 ` Jouni Malinen
2011-02-07 21:02 ` Ben Greear
2011-02-07 23:53 ` Daniel Halperin
2011-02-08 0:38 ` Ben Greear
2011-02-09 13:22 ` Jouni Malinen
2011-02-07 18:23 ` Ben Greear
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=4D4F0D83.4040401@candelatech.com \
--to=greearb@candelatech.com \
--cc=dhalperi@cs.washington.edu \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.org \
/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).