From: Helmut Schaa <helmut.schaa@googlemail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Helmut Schaa <helmut.schaa@googlemail.com>,
linville@tuxdriver.com, linux-wireless@vger.kernel.org,
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:19:02 +0100 [thread overview]
Message-ID: <200811260919.03118.helmut.schaa@gmail.com> (raw)
In-Reply-To: <1227641737.24264.5.camel@localhost.localdomain>
Am Dienstag, 25. November 2008 schrieb Dan Williams:
> On Tue, 2008-11-25 at 18:09 +0100, Helmut Schaa wrote:
> > I have no idea in which situations the scan takes longer than 5 seconds to
> > complete but maybe it might even take longer than 10 seconds. Has anybody from
> > Intel insight into the firmware scan code?
>
> Probably because with 802.11a, you have so many more channels to scan.
> Depending on whether they are active or passive, you may be able to do
> probe-scans on them, or you may have to sit on each channel for 120ms to
> listen for beacons. It's not unusual for cards that support A channels
> to take two or three times as long for a scan as cards that support only
> b/g, depending on the channel list.
Sure, but the strange thing is that not every scan took longer than 5 seconds.
I did not run much measurements but some scans even finished in less than 3
seconds.
Helmut
next prev parent reply other threads:[~2008-11-26 8:19 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 [this message]
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
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=200811260919.03118.helmut.schaa@gmail.com \
--to=helmut.schaa@googlemail.com \
--cc=dcbw@redhat.com \
--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).