linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: eddie@ehuk.net
Cc: stable@vger.kernel.org, florian@reitmeir.org,
	linux-wireless@vger.kernel.org, j@w1.fi
Subject: Re: Linux 3.6.5
Date: Tue, 06 Nov 2012 20:20:34 +0100	[thread overview]
Message-ID: <1352229634.8814.8.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <50995E25.6080601@ehuk.net>

On Tue, 2012-11-06 at 18:59 +0000, Eddie Chapman wrote:
> On 06/11/12 15:54, Johannes Berg wrote:
> > The problem here is that some devices (notably iwlwifi) will not allow
> > (by firmware) to connect to such an AP as HT40- if that is not allowed.
> > So I prevented it generally, but we can make it device dependent. I
> > don't like it much, but I suppose we can do it. Try this patch:
> >
> > http://p.sipsolutions.net/0129f39c7d882289.txt
> >
> > It will still prohibit this configuration when the driver said it's not
> > allowed, but will allow it when there were other reasons to not allow
> > it.
> 
> Just to report, with the patch under discussion re-applied 
> (3a40414f826a8f1096d9b94c4a53ef91b25ba28d), plus the patch at your link 
> above, my throughput is back to normal again.

Ok, thanks.

> So I guess the above patch resolves the issue (on the face of it) for 
> me, but whether it is a suitable solution I've no idea.

Right, we're still looking at that. It seems that it's not an ideal
solution, the regulatory change I proposed is probably better. Could you
check if it helps as well? That is, remove this patch, and apply this
one: http://p.sipsolutions.net/8877cbe3440d94b1.txt

johannes


  reply	other threads:[~2012-11-06 19:20 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121031173811.GA12970@kroah.com>
     [not found] ` <509575F4.5020109@ehuk.net>
     [not found]   ` <20121105081757.GA3730@kroah.com>
2012-11-05 11:04     ` Linux 3.6.5 Eddie Chapman
2012-11-05 12:01       ` Johannes Berg
2012-11-05 22:08         ` Eddie Chapman
2012-11-06  7:57           ` Johannes Berg
2012-11-06 15:34             ` Eddie Chapman
2012-11-06 15:54               ` Johannes Berg
2012-11-06 16:23                 ` Eddie Chapman
2012-11-06 16:39                 ` Johannes Berg
2012-11-06 16:47                   ` Johannes Berg
2012-11-06 16:50                   ` Eddie Chapman
2012-11-06 16:55                     ` Johannes Berg
2012-11-06 16:57                       ` Johannes Berg
2012-11-06 17:07                         ` Eddie Chapman
2012-11-06 17:16                           ` Johannes Berg
2012-11-06 18:59                 ` Eddie Chapman
2012-11-06 19:20                   ` Johannes Berg [this message]
2012-11-06 19:35                     ` Eddie Chapman
2012-11-06 20:31                       ` Johannes Berg
2012-11-06 20:38                         ` Eddie Chapman
2012-11-07  7:36                         ` Greg KH
2012-11-07  7:53                           ` Johannes Berg
2012-11-07  8:09                             ` Greg KH

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=1352229634.8814.8.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=eddie@ehuk.net \
    --cc=florian@reitmeir.org \
    --cc=j@w1.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@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).