From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/3] iwl3945: disable 11a support
Date: Thu, 20 Dec 2012 16:26:27 +0100 [thread overview]
Message-ID: <1356017187.10029.18.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20121220144549.GA10276@redhat.com>
On Thu, 2012-12-20 at 15:45 +0100, Stanislaw Gruszka wrote:
> On Thu, Dec 20, 2012 at 02:40:19PM +0100, Johannes Berg wrote:
> > On Thu, 2012-12-20 at 14:31 +0100, Stanislaw Gruszka wrote:
> > > I don't believe if there still are users using 11a mode. If they are,
> > > they should probably update their network to something that was
> > > designed in current century, but I also left module option for them.
> >
> > Huh? All of VHT etc. is going to use 5 GHz and will be compatible with
> > legacy clients, so having 11a support will allow them to connect to new
> > networks? Or am I midunderstanding what you're doing here?
>
> Yes, this disable 5GHz for 3945. I assumed this is not and will not be
> used anymore, but seems I was wrong.
>
> BTW: I'm not expect that 11ac AP will work good with 11a, i.e. I'm not
> able to connect to mixed network 11a & 11n on my 5GHz AP, but at least
> this should be theoretically possible.
>
> What I'm looking for is possibility to disable 5GHz to avoid network
> traffic delays while scanning, but this should be done in cfg80211.
Sounds more like a policy decision in wpa_s?
johannes
next prev parent reply other threads:[~2012-12-20 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 13:31 [PATCH 1/3] iwlegacy: add flush callback Stanislaw Gruszka
2012-12-20 13:31 ` [PATCH 2/3] iwl3945: disable 11a support Stanislaw Gruszka
2012-12-20 13:40 ` Johannes Berg
2012-12-20 14:45 ` Stanislaw Gruszka
2012-12-20 15:26 ` Johannes Berg [this message]
2012-12-20 16:09 ` Adrian Chadd
2012-12-20 13:31 ` [PATCH 3/3] iwlegacy: allow to enable PS Stanislaw Gruszka
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=1356017187.10029.18.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=sgruszka@redhat.com \
/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).