From: Johannes Berg <johannes@sipsolutions.net>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
Ben Cahill <ben.m.cahill@intel.com>, Zhu Yi <yi.zhu@intel.com>
Subject: Re: [PATCH 04/12] iwlwifi: document scan command
Date: Wed, 16 Jan 2008 01:02:52 +0100 [thread overview]
Message-ID: <1200441772.5887.167.camel@johannes.berg> (raw)
In-Reply-To: <1200361585-31801-5-git-send-email-reinette.chatre@intel.com> (sfid-20080115_022705_457944_D9860755)
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
> +/**
> + * struct iwl3945_scan_channel - entry in REPLY_SCAN_CMD channel table
> + *
> + * One for each channel in the scan list.
> + * Each channel can independently select:
> + * 1) SSID for directed active scans
> + * 2) Txpower setting (for rate specified within Tx command)
> + * 3) How long to stay on-channel (behavior may be modified by quiet_time,
> + * quiet_plcp_th, good_CRC_th)
This reminds me. How did you arrive at the dwell time? With hostapd
running on b43 I've frequently seen the dwell time being too low:
iwl4965 will transmit a probe request and go to the next channel before
hostapd sends the probe response, iwl4965 still sees the response, but
the b43 card never sees the ACK because it's receiver isn't quite as
good as the iwl4965 receiver.
Are there any restrictions in IEEE 802.11 on how fast probe responses
must be transmitted?
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2008-01-16 15:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 1:46 [PATCH 00/12] iwlwifi driver updates Reinette Chatre
2008-01-15 1:46 ` [PATCH 01/12] iwl4965: Remove redundant code in iwl4965_tx_cmd Reinette Chatre
2008-01-15 1:46 ` [PATCH 02/12] iwlwifi: move iwl4965_get_dma_hi_address function to iwl-helpers.h Reinette Chatre
2008-01-15 1:46 ` [PATCH 03/12] iwlwifi: remove iwl4965_tx_cmd Reinette Chatre
2008-01-15 1:46 ` [PATCH 04/12] iwlwifi: document scan command Reinette Chatre
2008-01-15 1:46 ` [PATCH 05/12] iwlwifi: delay firmware loading from pci_probe to network interface open Reinette Chatre
2008-01-15 1:46 ` [PATCH 06/12] iwlwifi: fix problem when rf_killswitch change during suspend/resume Reinette Chatre
2008-01-15 1:46 ` [PATCH 07/12] iwlwifi: move uCode helper functions to iwl-helpers.h Reinette Chatre
2008-01-15 1:46 ` [PATCH 08/12] iwlwifi: 4965 unify rate scale variable names for station data Reinette Chatre
2008-01-15 1:46 ` [PATCH 09/12] iwlwifi: 3954 renames iwl3945_rate_scale_priv to iwl3945_rs_sta Reinette Chatre
2008-01-15 1:46 ` [PATCH 10/12] iwlwifi: Update iwlwifi version stamp to 1.2.23 Reinette Chatre
2008-01-15 1:46 ` [PATCH 11/12] iwlwifi: remove reference to non-existent documentation Reinette Chatre
2008-01-15 1:46 ` [PATCH 12/12] iwlwifi: style fixes to usage of << and >> operators Reinette Chatre
2008-01-18 12:35 ` [PATCH 05/12] iwlwifi: delay firmware loading from pci_probe to network interface open Johannes Berg
2008-01-18 16:15 ` [PATCH 05/12] iwlwifi: delay firmware loading from pci_probeto " Chatre, Reinette
2008-01-16 0:02 ` Johannes Berg [this message]
2008-01-18 16:34 ` [PATCH 04/12] iwlwifi: document scan command Cahill, Ben M
2008-01-18 20:39 ` Johannes Berg
2008-01-21 15:51 ` Cahill, Ben M
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=1200441772.5887.167.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=ben.m.cahill@intel.com \
--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