linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: Felix Fietkau <nbd@openwrt.org>,
	linux-wireless@vger.kernel.org, linville@tuxdriver.com
Subject: Re: [PATCH] mac80211: fix channel type recalculation with HT and non-HT interfaces
Date: Fri, 11 Mar 2011 21:34:06 +0100	[thread overview]
Message-ID: <1299875646.4320.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D7A85FC.4090708@candelatech.com>

On Fri, 2011-03-11 at 12:28 -0800, Ben Greear wrote:

> > But I'm not sure what you mean?
> >
> > With the fix, we go through and use the widest possible channel of all
> > interfaces. The only conflict can happen with HT40- and HT40+, but we
> > should never get into that situation since we can't have one interface
> > with HT40- and another with HT40+ at the same time to start with. Am I
> > missing something?
> 
> Maybe I'm missing something, but from what I can tell:
> 
> If we have two interfaces:
> 
> first interface is HT40, second is HT20:
>    -> superchan == HT20
> 
> first interface is HT20, second is HT40:
>    -> superchan == HT40
> 
> It seems wrong that the ordering would influence superchan before we go into
> the "switch (superchan)" logic.

Ah, you're right -- the real fix isn't this patch, but probably
something like this:

...
case NL..._NO_HT:
case NL_...HT20:
	if (channel_type < super_chan)
		break;
	superchan = channel_type;
	break;
...

johannes


      reply	other threads:[~2011-03-11 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 20:05 [PATCH] mac80211: fix channel type recalculation with HT and non-HT interfaces Felix Fietkau
2011-03-11 20:17 ` Ben Greear
2011-03-11 20:24   ` Johannes Berg
2011-03-11 20:28     ` Ben Greear
2011-03-11 20:34       ` Johannes Berg [this message]

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=1299875646.4320.8.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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).