All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: drago01 <drago01@gmail.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ipw3945-devel@lists.sourceforge.net"
	<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/2] iwlwifi: use long monitor timer to avoid un-necessary reload
Date: Wed, 18 Aug 2010 12:30:55 -0700	[thread overview]
Message-ID: <1282159855.27858.1.camel@wwguy-huron> (raw)
In-Reply-To: <AANLkTikEKbHNtG0A=QdoxytSyBpG247=zdXOj1FmQ8Lw@mail.gmail.com>

On Wed, 2010-08-18 at 11:50 -0700, drago01 wrote:
> On Wed, Aug 18, 2010 at 7:50 PM, Wey-Yi Guy <wey-yi.w.guy@intel.com> wrote:
> > From: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> >
> > For 5000 series of devices, use long monitor timer to check
> > stuck tx queues.
> >
> > 5000 series device, it is being reported firmware got reload more
> > often than necessary, so extend the timer to avoid un-necessary reload.
> 
> What about iwl5300 ?
> As I noted in the other thread my 5300 was affected by said issue and
> increasing the timeout fixed it.
> 
I am not aware of 5300 also having similar issues; I all submit follow
up patch to extend the timeout value for 5300 device.

Thanks
Wey



  reply	other threads:[~2010-08-18 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 17:50 [PATCH 0/2] iwlwifi fix for stable kernel 2.6.35 Wey-Yi Guy
2010-08-18 17:50 ` [PATCH 1/2] iwlwifi: long monitor timer Wey-Yi Guy
2010-08-18 17:50 ` [PATCH 2/2] iwlwifi: use long monitor timer to avoid un-necessary reload Wey-Yi Guy
2010-08-18 18:50   ` drago01
2010-08-18 19:30     ` Guy, Wey-Yi [this message]
2010-08-18 19:31       ` drago01
  -- strict thread matches above, loose matches on Subject: below --
2010-08-14 15:45 [PATCH 0/2] iwlwifi fix for 2.6.35 Wey-Yi Guy
2010-08-14 15:45 ` [PATCH 2/2] iwlwifi: use long monitor timer to avoid un-necessary reload Wey-Yi Guy

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=1282159855.27858.1.camel@wwguy-huron \
    --to=wey-yi.w.guy@intel.com \
    --cc=drago01@gmail.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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.