From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Multiple vifs and HT v/s non-HT.
Date: Fri, 28 Jan 2011 14:17:43 +0100 [thread overview]
Message-ID: <1296220663.5118.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4D41FACB.2010807@candelatech.com>
On Thu, 2011-01-27 at 15:07 -0800, Ben Greear wrote:
> We found something fun while playing with HT mode:
>
> We had some vifs associated with an AP with HT enabled,
> and other VIFS to an AP with HT disabled.
>
> They managed to associate, but with slow rates and
> for whatever reason, nothing is able to send traffic.
> I would have expected one set or the other would
> be able to send traffic.
>
> The ath9k hardware ended up in HT mode according to
> ath9k debugfs wiphy file, but that was probably
> just luck.
>
> I'm not too sure how to ensure this mixed-mode HT
> scenario doesn't happen at this point...
So that patch you sent addressed this?
johannes
next prev parent reply other threads:[~2011-01-28 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 23:07 Multiple vifs and HT v/s non-HT Ben Greear
2011-01-28 13:17 ` Johannes Berg [this message]
2011-01-28 17:11 ` 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=1296220663.5118.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.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).