Linux wireless drivers development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Wey-Yi Guy <wey-yi.w.guy@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	ipw3945-devel@lists.sourceforge.net
Subject: Re: [PATCH 0/2] iwlwifi fix for 2.6.35
Date: Sat, 14 Aug 2010 21:42:33 +0200	[thread overview]
Message-ID: <1281814953.23399.29.camel@localhost.localdomain> (raw)
In-Reply-To: <1281800751-20784-1-git-send-email-wey-yi.w.guy@intel.com>

Hi Wey-Yi,

> When tx queue stuck, iwlwifi driver should detect and reload the firmware;
> different devices has different timing requirement, change the timeout
> value for 5000 series devices to avoid un-necessary firmware reload which
> can cause device become unstable.
> 
> This fixes:
> http://article.gmane.org/gmane.linux.kernel.wireless.general/53552
> 
> Wey-Yi Guy (2):
>   iwlwifi: long monitor timer
>   iwlwifi: use long monitor timer to avoid un-necessary reload

I think these qualify even to all -stable trees. I have at least seen it
with a 2.6.33.6 kernel from Fedora 13.

Regards

Marcel



  parent reply	other threads:[~2010-08-14 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 15:45 [PATCH 0/2] iwlwifi fix for 2.6.35 Wey-Yi Guy
2010-08-14 15:45 ` [PATCH 1/2] iwlwifi: long monitor timer Wey-Yi Guy
2010-08-14 15:45 ` [PATCH 2/2] iwlwifi: use long monitor timer to avoid un-necessary reload Wey-Yi Guy
2010-08-14 19:42 ` Marcel Holtmann [this message]
2010-08-14 21:53   ` [PATCH 0/2] iwlwifi fix for 2.6.35 Guy, Wey-Yi W
  -- strict thread matches above, loose matches on Subject: below --
2010-08-18 16:35 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=1281814953.23399.29.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=wey-yi.w.guy@intel.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