All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	Stanislaw Gruszka <sgruszka@redhat.com>,
	Intel Linux Wireless <ilw@linux.intel.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: add option to disable 5GHz band
Date: Thu, 19 Apr 2012 10:06:17 -0700	[thread overview]
Message-ID: <1334855177.27767.152.camel@wwguy-huron> (raw)
In-Reply-To: <1334851014.16897.297.camel@aeonflux>

On Thu, 2012-04-19 at 17:56 +0200, Marcel Holtmann wrote:
> Hi Johannes,
> 
> > > 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? Today, our driver 
> > may be the only one having this problem (which I've never really heard 
> > about?), but is it always going to be?
> 
> honestly I have seen 5GHz problems with our driver multiple times. I
> always ended up disabling 5GHz support in the AP since I rarely have
> time to debug this. It only happens after long time of operation for me,
> but was like super annoying all the time.
> 
> And I had similar issues with N support.
> 
> I would personally be fine with a global debugfs option within cfg80211
> to disable it.
> 
> Regards
> 
I don't see it hurt we have the option to disable the %GHz support in
iwlwifi. We could always change it later.

Thanks
Wey


  reply	other threads:[~2012-04-19 17:10 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 [this message]
2012-04-20  7:36   ` 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=1334855177.27767.152.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.