From: Mohamed Abbas <mabbas@linux.intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Hong Liu <hong.liu@intel.com>,
netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 2/2]d80211: add hardware scan callback
Date: Wed, 30 Aug 2006 11:36:14 -0700 [thread overview]
Message-ID: <44F5DA9E.9080103@linux.intel.com> (raw)
In-Reply-To: <20060830191058.14275f74@griffin.suse.cz>
3945 firmware and hardware still do time critical functions like
Beaconing and power management. This restrict us once associated to
switch channel from the driver. we need to unassociated first before
switching to a new channel. Because of this restriction while
associated we can only call scan command and the firmware will take of
tunning to available channels to listen to beacon and prob_resp.
Jiri Benc wrote:
>On Fri, 25 Aug 2006 16:32:13 +0800, Hong Liu wrote:
>
>
>>Add hardware scan callback to support cards like ipw3945 which
>>implements the scan command in firmware.
>>
>>
>
>How ipw3945 performs scan? From the patch, it looks like it switches
>channels (and sends probe requests) in the firmware and delivers all
>received beacons and probe responses through the normal rx path to be
>handled in a software MAC layer. This is really weird behaviour and
>doesn't make sense to me. Why isn't channel switching left to the
>software MAC as well?
>
>
>
>>+/* set station scan completed */
>>+void ieee80211_set_scan_completed(struct net_device *dev);
>>
>>
>
>Why "set"? "ieee80211_scan_completed" sounds better.
>
>Thanks,
>
> Jiri
>
>
>
next prev parent reply other threads:[~2006-08-30 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 8:32 [PATCH 2/2]d80211: add hardware scan callback Hong Liu
2006-08-29 12:08 ` Johannes Berg
2006-08-30 17:10 ` Jiri Benc
2006-08-30 18:36 ` Mohamed Abbas [this message]
2006-09-01 3:37 ` Hong Liu
2006-09-01 6:41 ` Johannes Berg
2006-09-01 7:34 ` Hong Liu
2006-09-21 19:22 ` Jiri Benc
2009-04-06 15:12 ` oterito
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=44F5DA9E.9080103@linux.intel.com \
--to=mabbas@linux.intel.com \
--cc=hong.liu@intel.com \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).