From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: add option to disable 5GHz band
Date: Fri, 20 Apr 2012 09:36:33 +0200 [thread overview]
Message-ID: <20120420073630.GA2393@redhat.com> (raw)
In-Reply-To: <4F901F51.3000704@sipsolutions.net>
On Thu, Apr 19, 2012 at 07:21:05AM -0700, Johannes Berg wrote:
> On 4/19/2012 3:11 AM, Stanislaw Gruszka wrote:
> >There are various problems happened on 5GHz band not observed on
> >2.4 GHz (microcode errors, queue stuck, etc... ) . Also roaming
> >between 5GHz AP and 2GHz does not work very well. To workaround
> >the problems add option to disable 5GHz support. This will help
> >on environments where APs are dual-band, and devices will not try
> >to associate on band where issues happen.
>
> Would it make sense to somehow do this in cfg80211?
It has more sense, but doing this in cfg80211 is a bit more complicated,
at least I do not see an easy way.
> Today, our
> driver may be the only one having this problem (which I've never
> really heard about?)
I filed bug 2351 on your bugzilla, which explicitly state issue it's
a 5GHz problem.
There are various other bug reports about iwlwifi random malfunction
(with no message in dmesg or queue stuck or microcode error). Some of
them are probably 5GHz problem too, but since nobody work on that
bugzillas nobody figure this out.
Regarding 2GHz <-> 5GHz roaming, I'm seeing lot's of problems with that
on older kernels. Did not test on new kernel though. Perhaps issues are
now mitigated or fixed by your assoc/auth redesign, but I did not check
yet.
Stanislaw
prev parent reply other threads:[~2012-04-20 7:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 10:11 [PATCH] iwlwifi: add option to disable 5GHz band Stanislaw Gruszka
2012-04-19 13:50 ` Guy, Wey-Yi
2012-04-19 14:02 ` Stanislaw Gruszka
2012-04-19 14:21 ` Johannes Berg
2012-04-19 15:56 ` Marcel Holtmann
2012-04-19 17:06 ` Guy, Wey-Yi
2012-04-20 7:36 ` Stanislaw Gruszka [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=20120420073630.GA2393@redhat.com \
--to=sgruszka@redhat.com \
--cc=ilw@linux.intel.com \
--cc=johannes@sipsolutions.net \
--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).