From: Stanislaw Gruszka <sgruszka@redhat.com>
To: 李朝明 <chaoming_li@realsil.com.cn>,
"Johannes Berg" <johannes@sipsolutions.net>
Cc: "'Larry Finger'" <Larry.Finger@lwfinger.net>,
"'John W Linville'" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org,
'冯春燕' <amyfcy_feng@realsil.com.cn>,
'熊光安' <guangan_xiong@realsil.com.cn>
Subject: Re: 答复: 答复: about Mac80211 scan issue
Date: Thu, 10 Feb 2011 10:50:06 +0100 [thread overview]
Message-ID: <20110210095006.GB2228@redhat.com> (raw)
In-Reply-To: <39A39FA0AD1A481480DE0BD469AAA79E@realsil.com.cn>
On Thu, Feb 10, 2011 at 03:48:57PM +0800, 李朝明 wrote:
> Yes, that flush can work well, but before drv_flush in
> ieee80211_start_sw_scan have no queue stop actions.
> Below are corresponding code:
> static int ieee80211_start_sw_scan(struct ieee80211_local *local)
> {
> /*
> * Hardware/driver doesn't support hw_scan, so use software
> * scanning instead. First send a nullfunc frame with power save
> * bit on so that AP will buffer the frames for us while we are not
> * listening, then send probe requests to each channel and wait for
> * the responses. After all channels are scanned, tune back to the
> * original channel and send a nullfunc frame with power save bit
> * off to trigger the AP to send us all the buffered frames.
> *
> * Note that while local->sw_scanning is true everything else but
> * nullfunc frames and probe requests will be dropped in
> * ieee80211_tx_h_check_assoc().
> */
> drv_sw_scan_start(local);
>
> ieee80211_offchannel_stop_beaconing(local);
>
> local->leave_oper_channel_time = 0;
> local->next_scan_state = SCAN_DECISION;
> local->scan_channel_idx = 0;
>
> drv_flush(local, false);
I looked at wireless-testing tree where code was currently
changed by b23b025fe246f3acc2988eb6d400df34c27cb8ae
"mac80211: Optimize scans on current operating channel."
We stop queues and flush only when leaving operating channel in
ieee80211_scan_state_leave_oper_channel(), what seems to be correct.
Regarding linux-2.6 tree. I think you have right and we have bug
in mac80211, because we do not stop queues before flush in
ieee80211_offchannel_stop_beaconing() when working in STA mode.
Also comment in above function seems to be wrong.
I'm not sure what to do with that, maybe Johannes will
have some insight?
Anyway, chaoming_li, could you clone current wireless-testing
tree and see how things work there?
next prev parent reply other threads:[~2011-02-10 9:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 18:44 [PATCH 2/6] rtlwifi: Add usb driver Larry Finger
2011-02-07 15:07 ` Stanislaw Gruszka
2011-02-07 15:12 ` Stanislaw Gruszka
2011-02-09 1:58 ` about Mac80211 scan issue 李朝明
2011-02-09 10:54 ` Stanislaw Gruszka
[not found] ` <B8DE8263FD784AC082CFDB7E9269BAEA@realsil.com.cn>
2011-02-10 7:41 ` 答复: " Stanislaw Gruszka
[not found] ` <39A39FA0AD1A481480DE0BD469AAA79E@realsil.com.cn>
2011-02-10 9:50 ` Stanislaw Gruszka [this message]
[not found] ` <86D43C3FD69641C38E7144E721BCC5A6@realsil.com.cn>
2011-02-10 11:37 ` 答复: 答复: 答复: about Mac80211scan issue Stanislaw Gruszka
2011-02-11 2:26 ` [RFC] mac80211: cisco 1252 HT bw20, sta->ht_cap.cap bw is wrong 李朝明
2011-02-11 10:22 ` Stanislaw Gruszka
2011-02-12 3:32 ` [RFC] mac80211: mac80211's null packet issue 李朝明
2011-02-14 10:16 ` Johannes Berg
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=20110210095006.GB2228@redhat.com \
--to=sgruszka@redhat.com \
--cc=Larry.Finger@lwfinger.net \
--cc=amyfcy_feng@realsil.com.cn \
--cc=chaoming_li@realsil.com.cn \
--cc=guangan_xiong@realsil.com.cn \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).