From: wwguy <wey-yi.w.guy@intel.com>
To: Cheng Renquan <crquan@gmail.com>
Cc: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs)
Date: Wed, 21 Dec 2011 17:40:57 -0800 [thread overview]
Message-ID: <1324518057.4755.4.camel@wwguy-ubuntu> (raw)
In-Reply-To: <CAH5vBdJ4-33z3FbOwVG1QRzfFOwFpz1wccbQNDXEC6-NhBa31A@mail.gmail.com>
Hi Renquan,
On Wed, 2011-12-21 at 15:28 -0800, Cheng Renquan wrote:
> I cherry-picked these 3 patches on top to v3.2.0-rc6, and now it's working,
> Thank you all everyone's effort;
>
> [archuser@archtop linux-git]$ git cherry-pick 123877b80
> [b46 55de35a] iwlwifi: do not set the sequence control bit is not needed
> Author: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> 1 files changed, 4 insertions(+), 1 deletions(-)
> [archuser@archtop linux-git]$ git cherry-pick 81670a49184
> [b46 1b0b51d] iwlwifi: tx_sync only on PAN context
> Author: Johannes Berg <johannes.berg@intel.com>
> 1 files changed, 6 insertions(+), 0 deletions(-)
> [archuser@archtop linux-git]$ git cherry-pick 78feb35b81
> [b46 73d79e2] iwlwifi: allow to switch to HT40 if not associated
> Author: Wey-Yi Guy <wey-yi.w.guy@intel.com>
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
Thank you for the update, I am glad works for you
>
> When walking to some corner meeting rooms (but still has good
> wifi connectivity, verified by another Android phone wifi ;),
> the roaming may be from previous AP to none and none to next AP,
> the process may need 1 to 2 minutes to be stable again, it's not
> ideally swift but acceptable,
>
>
Yes, I know we have more works to do on roaming, it is on our to-do list
Thanks
Wey
> Dec 21 14:59:11 archtop NetworkManager[2333]: <info> (wlan0): roamed
> from BSSID 24:B6:57:34:CC:5F (blizzard) to 6C:9C:ED:EC:BC:7F
> (blizzard)
> Dec 21 14:59:41 archtop NetworkManager[2333]: <info> (wlan0): roamed
> from BSSID 6C:9C:ED:EC:BC:7F (blizzard) to (none) ((none))
> Dec 21 14:59:53 archtop NetworkManager[2333]: <info> (wlan0): roamed
> from BSSID (none) ((none)) to 2C:3F:38:F6:A8:AF (blizzard)
>
>
> Thanks,
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-12-22 1:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 23:20 linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs) Cheng Renquan
2011-12-20 23:46 ` Guy, Wey-Yi
2011-12-21 2:37 ` Cheng Renquan
2011-12-21 6:22 ` Sedat Dilek
2011-12-21 8:03 ` Cheng Renquan
2011-12-21 8:53 ` Sedat Dilek
2011-12-21 9:06 ` Cheng Renquan
2011-12-21 9:20 ` Sedat Dilek
2011-12-21 10:36 ` Cheng Renquan
2011-12-21 11:14 ` Sedat Dilek
2011-12-21 16:14 ` Guy, Wey-Yi
2011-12-21 23:28 ` Cheng Renquan
2011-12-22 1:40 ` wwguy [this message]
2012-01-10 23:17 ` Cheng Renquan
2012-01-10 22:27 ` Guy, Wey-Yi
2012-01-11 0:01 ` Cheng Renquan
2012-01-10 23:20 ` Guy, Wey-Yi
2012-01-11 1:30 ` Cheng Renquan
2012-01-11 2:28 ` wwguy
2012-01-11 16:37 ` wwguy
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=1324518057.4755.4.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=crquan@gmail.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sedat.dilek@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.