From: Kalle Valo <kalle.valo@nokia.com>
To: "Holger Schurig" <hs4233@mail.mn-solutions.de>
Cc: linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>,
linville@tuxdriver.com, yi.zhu@intel.com,
reinette.chatre@intel.com, ipw2100-devel@lists.sourceforge.net
Subject: Re: [PATCH] ipw2200: increase scan timeout
Date: Wed, 26 Nov 2008 09:24:59 +0200 [thread overview]
Message-ID: <87bpw3ar04.fsf@nokia.com> (raw)
In-Reply-To: <200811260706.03160.hs4233@mail.mn-solutions.de> (ext Holger Schurig's message of "Wed\, 26 Nov 2008 07\:06\:03 +0000")
Holger Schurig <hs4233@mail.mn-solutions.de> writes:
> Second thing: why should the association get's cleared if the
> adapter get's reset? Isn't one a (assoc) at protocol level and
> the other (adapter) a hardware thing?
Good point. I once had a bad bug in stlc45xx tx queue handling and
firmware was crashing all the time. 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.
--
Kalle Valo
next prev parent reply other threads:[~2008-11-26 7:25 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 [this message]
2008-11-26 8:04 ` Zhu Yi
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=87bpw3ar04.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=helmut.schaa@googlemail.com \
--cc=hs4233@mail.mn-solutions.de \
--cc=ipw2100-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=yi.zhu@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;
as well as URLs for NNTP newsgroup(s).