Re: linux 3.2-rcX iwlwifi driver's problem (wifi link unstable when moving between multiple APs)

["Guy, Wey-Yi" <wey-yi.w.guy@intel.com>]

Hi Renquan,

On Wed, 2011-12-21 at 03:14 -0800, Sedat Dilek wrote:
> On Wed, Dec 21, 2011 at 11:36 AM, Cheng Renquan <crquan@gmail.com> wrote:
> > On Wed, Dec 21, 2011 at 1:20 AM, Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> [...]
> > read these from MAINTAINERS, just want to confirm if iwlwifi.git has more
> > fresh content, this should be the most upstream, right?
> >
> 
> Wey-Yi or Johannes can gave you precise answers on iwwifi development.
> Of course the iwlwifi GIT (master) tree has latest stuff.
> As you might have seen there are different GIT branches for stuff to
> go into wireless-testing (experimental sofware), wireless-next
> (linux-next.git) and wireless (linux.git).
> 
http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi.git;a=summary
contain the latest patches(both features and bugs fix) which being
updates on daily base. Like Sadet mention, those are experimental and
not being fully test yet. Once those new patches pass the basic
regression test. the patches will push into two different tree
wireless-next : patch contain new features
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=summary
wireless: bug fix patch
http://git.kernel.org/?p=linux/kernel/git/linville/wireless.git;a=summary
Linville also merge  both wireless-next and wireless  tree  into
wireless-testing for people who want to test the breeding edge wireless
driver changes
http://git.kernel.org/?p=linux/kernel/git/linville/wireless-testing.git;a=summary

of cause, Linville will push the patches to both net-next and net tree
once he believe the patches are ready.

> > (only here has new fix and fixes are verified correct, then John Linville could
> > pull from here the iwlwifi.git, right? As I understand, the MAINTAINERS model
> > should be the way of iwlwifi.git => wireless.git => net.git => linus)
> >
> 
> For mainline this workflow seems to be correct, but AFAICS you want an
> official statement, so wait for Wey-Yi's answer :-).
> 
> > INTEL WIRELESS WIFI LINK (iwlwifi)
> > M:      Wey-Yi Guy <wey-yi.w.guy@intel.com>
> > M:      Intel Linux Wireless <ilw@linux.intel.com>
> > L:      linux-wireless@vger.kernel.org
> > W:      http://intellinuxwireless.org
> > T:      git git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi.git
> > S:      Supported
> > F:      drivers/net/wireless/iwlwifi/
> >
> >
> > By comparing the two, I got that iwlwifi.git really has more, now
> > prefetched for tomorrow
> > when in office sometimes Internet is not available, and in case
> > wireless.git with your patch
> > still does not work, I could have a try of iwlwifi.git;
> >
> 
> If you want latest iwlwifi bits, you can try also the work from there.
> But a better strategy would be to test this order:
> 1. wireless (stable)
> 2. wireless-next or linux-next (testing)
> 3. wireless-testing and/or wiwlwifi (experimental)
> 
wireless-testing = wireless + wireless-next

Thanks
Wey

> - Sedat -
> 
> > http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi.git;a=history;f=drivers/net/wireless/iwlwifi
> > http://git.kernel.org/?p=linux/kernel/git/linville/wireless.git;a=history;f=drivers/net/wireless/iwlwifi
> >
> [...]