From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from rv-out-0506.google.com ([209.85.198.230]:28609 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751050AbZERSWj (ORCPT ); Mon, 18 May 2009 14:22:39 -0400 Received: by rv-out-0506.google.com with SMTP id f6so957657rvb.5 for ; Mon, 18 May 2009 11:22:40 -0700 (PDT) MIME-Version: 1.0 From: "Luis R. Rodriguez" Date: Mon, 18 May 2009 11:22:17 -0700 Message-ID: <43e72e890905181122w38f83785p2134a5142a9f0905@mail.gmail.com> Subject: Plan of attack for enhancements for scan while associated To: Senthil Balasubramanian , Helmut Schaa Cc: linux-wireless , Aeolus.Yang@atheros.com, Gaurav.Jauhar@atheros.com Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Helmut, Senthil has indicated interest in working on this, Johannes had pointed out you might have some initial work on this already? Can you post your patch, it might help? Just so we're clear this would be an enhancement for wext/nl80211 regular scan -- when we're associated we'd do scans by going to a new channel and then coming back to our operating channel to able to receive frames. We'd do this for each channel we can scan on until we're done with all of them. We could possibly allow for a debugfs parameters to allow users to tune this to say scan over x channels before going to the operating channel, as well as change the time between moving to a new channel. This would probably help mostly with tuning this while debugging or figuring out ideal default values. New userspace can simply make use of nl80211 scan on an individual freq request and figure things out on its own. Luis