linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Javier Cardona <javier@cozybit.com>,
	Alexander Simon <an.alexsimon@googlemail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v3 3/3] mac80211: Add HT operation modes for IBSS
Date: Tue, 20 Sep 2011 23:52:59 +0200	[thread overview]
Message-ID: <4E790B3B.9090004@openwrt.org> (raw)
In-Reply-To: <CAB=NE6W76dg_KaN6jB-OQ2xf7Xx93a4ruqzQDwg5+rcwOcSfXg@mail.gmail.com>

On 2011-09-20 11:26 PM, Luis R. Rodriguez wrote:
> On Tue, Sep 20, 2011 at 2:04 PM, Felix Fietkau<nbd@openwrt.org>  wrote:
>>  If we want to properly enforce Annex J channel pairs, this needs to
>>  be moved to cfg80211.
>
> This does not still address the issue of one peer finding out it
> cannot deal with an HT40 pair and correcting the topology and
> propagating this out. Not yet sure if for 802.11ac we'll need
> something similar but its worth considering.
Don't think of it as a topology. Each node makes its own decisions about 
HT40+/HT40-/HT20. If modes are incompatible, fallback to HT20  always 
works for communicating with a peer.

- Felix

  parent reply	other threads:[~2011-09-20 21:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17 22:14 [PATCH v3 1/3] nl80211: Parse channel type attribute in an ibss join request Alexander Simon
2011-09-17 22:14 ` [PATCH v3 2/3] mac80211: Add HT helper functions Alexander Simon
2011-09-19 12:55   ` Johannes Berg
2011-09-19 13:01     ` Alexander Simon
2011-09-17 22:14 ` [PATCH v3 3/3] mac80211: Add HT operation modes for IBSS Alexander Simon
2011-09-17 22:54   ` Alexander Simon
2011-09-19 13:04     ` Johannes Berg
2011-09-19 15:46       ` Alexander Simon
2011-09-20 12:21         ` Johannes Berg
2011-09-20 18:12           ` Luis R. Rodriguez
2011-09-20 18:21             ` Felix Fietkau
2011-09-20 18:38               ` Luis R. Rodriguez
2011-09-20 18:46                 ` Felix Fietkau
2011-09-20 19:05                   ` Luis R. Rodriguez
2011-09-20 19:31                     ` Felix Fietkau
2011-09-20 20:18                       ` Luis R. Rodriguez
2011-09-20 21:04                         ` Felix Fietkau
2011-09-20 21:26                           ` Luis R. Rodriguez
2011-09-20 21:52                             ` Luis R. Rodriguez
2011-09-20 22:09                               ` Felix Fietkau
2011-09-20 22:39                                 ` Luis R. Rodriguez
2011-09-20 21:52                             ` Felix Fietkau [this message]
2011-09-20 22:37                               ` Luis R. Rodriguez
2011-09-20 22:54                                 ` Felix Fietkau
2011-09-20 23:04                                   ` Luis R. Rodriguez
2011-09-20 18:55               ` Javier Cardona
2011-09-19 12:52 ` [PATCH v3 1/3] nl80211: Parse channel type attribute in an ibss join request Johannes Berg
2011-09-19 13:18   ` Alexander Simon
2011-09-19 13:32     ` 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=4E790B3B.9090004@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=an.alexsimon@googlemail.com \
    --cc=javier@cozybit.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@frijolero.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).