All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Yi <yi.zhu@intel.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: Holger Schurig <hs4233@mail.mn-solutions.de>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Helmut Schaa <helmut.schaa@googlemail.com>,
	"linville@tuxdriver.com" <linville@tuxdriver.com>,
	"Chatre, Reinette" <reinette.chatre@intel.com>,
	"ipw2100-devel@lists.sourceforge.net"
	<ipw2100-devel@lists.sourceforge.net>
Subject: Re: [PATCH] ipw2200: increase scan timeout
Date: Wed, 26 Nov 2008 16:04:34 +0800	[thread overview]
Message-ID: <1227686674.2548.398.camel@debian.sh.intel.com> (raw)
In-Reply-To: <87bpw3ar04.fsf@nokia.com>

On Wed, 2008-11-26 at 15:24 +0800, Kalle Valo wrote:
> While the firmware was reset
> association state wasn't changed and I could, for example, run iperf
> tests while firmware was resetting without userspace noticing anything
> (expect a slight decreare of throughput of course). This might depend
> on firmware implementation, but at least with softmac devices it
> shouldn't be a problem.

This is fairly easy to be handled by hardmac as well. We didn't do it
because: 1) this is an unexpected behaviour so we simply put everything
to the initial state when this happens and didn't put a lot of effort on
the recovery 2) 'associate=1' used to be the default value, so the
driver associated automatically after the firmware restart cycle.

Patches are welcome.

Thanks,
-yi


  reply	other threads:[~2008-11-26  8:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 17:09 [PATCH] ipw2200: increase scan timeout Helmut Schaa
2008-11-25 18:32 ` reinette chatre
2008-11-25 22:06   ` [Ipw2100-devel] " Cahill, Ben M
2008-11-26  8:21   ` Helmut Schaa
2008-11-26 16:28   ` Helmut Schaa
2008-11-25 19:35 ` Dan Williams
2008-11-26  8:19   ` Helmut Schaa
2008-11-25 22:17 ` [Ipw2100-devel] " Harald Braumann
2008-11-26  8:13   ` Helmut Schaa
2008-11-26  7:06 ` Holger Schurig
2008-11-26  7:24   ` Kalle Valo
2008-11-26  8:04     ` Zhu Yi [this message]
2008-11-26 16:19       ` Dan Williams
2008-11-26  8:09   ` Helmut Schaa

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=1227686674.2548.398.camel@debian.sh.intel.com \
    --to=yi.zhu@intel.com \
    --cc=helmut.schaa@googlemail.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=ipw2100-devel@lists.sourceforge.net \
    --cc=kalle.valo@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=reinette.chatre@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 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.